From f799942d8887880afe98958c84c006f94ea4a887 Mon Sep 17 00:00:00 2001 From: Robert Lipe Date: Wed, 5 Jan 2022 20:38:56 -0600 Subject: [PATCH] Remove trailing space in xmldoc/. sed --in-place 's/[[:space:]]\+$//' $* This is only the xmldoc part of 9935496f5c8c772ea11785ff489768dbb2de5d4f --- xmldoc/babelmain.xsl | 16 ++--- xmldoc/filters/arc.xml | 44 ++++++------ xmldoc/filters/bend.xml | 2 +- xmldoc/filters/discard.xml | 6 +- xmldoc/filters/duplicate.xml | 22 +++--- xmldoc/filters/height.xml | 12 ++-- xmldoc/filters/interpolate.xml | 6 +- xmldoc/filters/nuketypes.xml | 4 +- xmldoc/filters/options/arc-distance.xml | 4 +- xmldoc/filters/options/arc-exclude.xml | 2 +- xmldoc/filters/options/arc-file.xml | 2 +- xmldoc/filters/options/arc-points.xml | 2 +- xmldoc/filters/options/discard-elemin.xml | 6 +- xmldoc/filters/options/discard-hdop.xml | 6 +- .../filters/options/discard-hdopandvdop.xml | 6 +- xmldoc/filters/options/discard-matchname.xml | 2 +- xmldoc/filters/options/discard-vdop.xml | 6 +- xmldoc/filters/options/duplicate-all.xml | 4 +- xmldoc/filters/options/duplicate-correct.xml | 12 ++-- xmldoc/filters/options/duplicate-location.xml | 8 +-- .../filters/options/duplicate-shortname.xml | 4 +- xmldoc/filters/options/interpolate-route.xml | 2 +- .../filters/options/nuketypes-waypoints.xml | 2 +- xmldoc/filters/options/polygon-exclude.xml | 2 +- xmldoc/filters/options/polygon-file.xml | 6 +- xmldoc/filters/options/position-distance.xml | 4 +- xmldoc/filters/options/position-time.xml | 4 +- xmldoc/filters/options/radius-asroute.xml | 4 +- xmldoc/filters/options/radius-distance.xml | 2 +- xmldoc/filters/options/radius-maxcount.xml | 18 ++--- xmldoc/filters/options/simplify-count.xml | 2 +- .../filters/options/simplify-crosstrack.xml | 4 +- xmldoc/filters/options/simplify-error.xml | 4 +- xmldoc/filters/options/simplify-length.xml | 2 +- xmldoc/filters/options/stack-append.xml | 2 +- xmldoc/filters/options/stack-copy.xml | 4 +- xmldoc/filters/options/stack-pop.xml | 6 +- xmldoc/filters/options/stack-push.xml | 2 +- xmldoc/filters/options/stack-replace.xml | 6 +- xmldoc/filters/options/track-course.xml | 6 +- xmldoc/filters/options/track-discard.xml | 4 +- xmldoc/filters/options/track-fix.xml | 2 +- xmldoc/filters/options/track-merge.xml | 8 +-- .../filters/options/track-minimum_points.xml | 2 +- xmldoc/filters/options/track-pack.xml | 4 +- xmldoc/filters/options/track-sdistance.xml | 20 +++--- xmldoc/filters/options/track-speed.xml | 4 +- xmldoc/filters/options/track-split.xml | 12 ++-- xmldoc/filters/options/track-start.xml | 12 ++-- xmldoc/filters/options/track-stop.xml | 8 +-- xmldoc/filters/options/track-title.xml | 10 +-- xmldoc/filters/options/transform-del.xml | 2 +- xmldoc/filters/options/transform-rptname.xml | 24 +++---- xmldoc/filters/options/transform-rte.xml | 2 +- xmldoc/filters/options/transform-trk.xml | 6 +- xmldoc/filters/options/transform-wpt.xml | 2 +- xmldoc/filters/options/validate-debug.xml | 2 +- xmldoc/filters/polygon.xml | 32 ++++----- xmldoc/filters/position.xml | 6 +- xmldoc/filters/radius.xml | 10 +-- xmldoc/filters/reverse.xml | 4 +- xmldoc/filters/simplify.xml | 24 +++---- xmldoc/filters/sort.xml | 2 +- xmldoc/filters/stack.xml | 42 ++++++------ xmldoc/filters/track.xml | 2 +- xmldoc/formats/arc.xml | 10 +-- xmldoc/formats/baroiq.xml | 4 +- xmldoc/formats/bcr.xml | 20 +++--- xmldoc/formats/bushnell.xml | 10 +-- xmldoc/formats/bushnell_trl.xml | 12 ++-- xmldoc/formats/cambridge.xml | 12 ++-- xmldoc/formats/coastexp.xml | 6 +- xmldoc/formats/csv.xml | 8 +-- xmldoc/formats/cup.xml | 6 +- xmldoc/formats/custom.xml | 2 +- xmldoc/formats/destinator_trl.xml | 4 +- xmldoc/formats/dg-100.xml | 8 +-- xmldoc/formats/dmtlog.xml | 6 +- xmldoc/formats/dna.xml | 2 +- xmldoc/formats/easygps.xml | 2 +- xmldoc/formats/energympro.xml | 6 +- xmldoc/formats/enigma.xml | 22 +++--- xmldoc/formats/enigma_wp.xml | 20 +++--- xmldoc/formats/exif.xml | 4 +- xmldoc/formats/f90g.xml | 2 +- xmldoc/formats/fit.xml | 4 +- xmldoc/formats/fugawi.xml | 6 +- xmldoc/formats/gdb.xml | 8 +-- xmldoc/formats/geo.xml | 10 +-- xmldoc/formats/geojson.xml | 8 +-- xmldoc/formats/ggv_log.xml | 6 +- xmldoc/formats/ggv_ovl.xml | 4 +- xmldoc/formats/glogbook.xml | 6 +- xmldoc/formats/googledir.xml | 12 ++-- xmldoc/formats/gpl.xml | 4 +- xmldoc/formats/gpsdrive.xml | 6 +- xmldoc/formats/gpsdrivetrack.xml | 6 +- xmldoc/formats/gpx.xml | 2 +- xmldoc/formats/gtrnctr.xml | 18 ++--- xmldoc/formats/hiketech.xml | 4 +- xmldoc/formats/holux.xml | 6 +- xmldoc/formats/hsandv.xml | 6 +- xmldoc/formats/html.xml | 6 +- xmldoc/formats/humminbird.xml | 8 +-- xmldoc/formats/iblue757.xml | 6 +- xmldoc/formats/ignrando.xml | 6 +- xmldoc/formats/igo2008_poi.xml | 2 +- xmldoc/formats/ik3d.xml | 2 +- xmldoc/formats/kml.xml | 14 ++-- xmldoc/formats/kompass_tk.xml | 2 +- xmldoc/formats/ktf2.xml | 2 +- xmldoc/formats/kwf2.xml | 12 ++-- xmldoc/formats/lmx.xml | 2 +- xmldoc/formats/m241-bin.xml | 12 ++-- xmldoc/formats/magellan.xml | 8 +-- xmldoc/formats/magellan1.xml | 6 +- xmldoc/formats/magellanx.xml | 10 +-- xmldoc/formats/mapasia_tr7.xml | 6 +- xmldoc/formats/mapbar.xml | 4 +- xmldoc/formats/mapconverter.xml | 6 +- xmldoc/formats/miniHomer.xml | 16 ++--- xmldoc/formats/mmo.xml | 2 +- xmldoc/formats/motoactv.xml | 2 +- xmldoc/formats/mtk-bin.xml | 6 +- xmldoc/formats/mtk.xml | 68 +++++++++---------- xmldoc/formats/mtk_locus.xml | 8 +-- xmldoc/formats/mxf.xml | 6 +- xmldoc/formats/navigonwpt.xml | 4 +- xmldoc/formats/navilink.xml | 6 +- xmldoc/formats/netstumbler.xml | 10 +-- xmldoc/formats/nima.xml | 6 +- xmldoc/formats/nmea.xml | 14 ++-- xmldoc/formats/openoffice.xml | 2 +- xmldoc/formats/options/bcr-index.xml | 6 +- xmldoc/formats/options/bcr-name.xml | 2 +- xmldoc/formats/options/bcr-radius.xml | 4 +- xmldoc/formats/options/cetus-appendicon.xml | 2 +- xmldoc/formats/options/delbin-gcsym.xml | 6 +- xmldoc/formats/options/delbin-hint_at_and.xml | 2 +- xmldoc/formats/options/delbin-hint_at_end.xml | 2 +- xmldoc/formats/options/delbin-logs.xml | 2 +- xmldoc/formats/options/delbin-long_notes.xml | 4 +- xmldoc/formats/options/delbin-nukewpt.xml | 2 +- xmldoc/formats/options/dmtlog-index.xml | 6 +- xmldoc/formats/options/exif-frame.xml | 2 +- xmldoc/formats/options/garmin-baud.xml | 6 +- .../formats/options/garmin-bitscategory.xml | 4 +- xmldoc/formats/options/garmin-resettime.xml | 4 +- xmldoc/formats/options/garmin-snwhite.xml | 2 +- xmldoc/formats/options/garmin_gpi-alerts.xml | 2 +- xmldoc/formats/options/garmin_gpi-bitmap.xml | 6 +- .../options/garmin_gpi-languagecode.xml | 2 +- .../formats/options/garmin_gpi-proximity.xml | 4 +- xmldoc/formats/options/garmin_gpi-sleep.xml | 4 +- xmldoc/formats/options/garmin_gpi-speed.xml | 4 +- xmldoc/formats/options/garmin_txt-date.xml | 2 +- xmldoc/formats/options/garmin_txt-datum.xml | 2 +- xmldoc/formats/options/garmin_txt-grid.xml | 6 +- xmldoc/formats/options/garmin_txt-time.xml | 2 +- xmldoc/formats/options/garmin_txt-utc.xml | 4 +- xmldoc/formats/options/gdb-bitscategory.xml | 4 +- xmldoc/formats/options/gdb-cat.xml | 2 +- xmldoc/formats/options/gdb-dropwpt.xml | 4 +- xmldoc/formats/options/gdb-roadbook.xml | 6 +- xmldoc/formats/options/gdb-via.xml | 4 +- xmldoc/formats/options/geo-deficon.xml | 6 +- xmldoc/formats/options/geojson-compact.xml | 2 +- .../formats/options/globalsat-dump-file.xml | 6 +- xmldoc/formats/options/gpssim-split.xml | 2 +- xmldoc/formats/options/gpx-elevprec.xml | 6 +- .../formats/options/gpx-garminextensions.xml | 2 +- xmldoc/formats/options/gpx-gpxver.xml | 4 +- xmldoc/formats/options/html-encrypt.xml | 2 +- xmldoc/formats/options/html-logs.xml | 2 +- xmldoc/formats/options/ignrando-index.xml | 6 +- xmldoc/formats/options/igo8-tracknum.xml | 2 +- xmldoc/formats/options/itracku-backup.xml | 2 +- xmldoc/formats/options/itracku-new.xml | 6 +- xmldoc/formats/options/kml-line_color.xml | 2 +- xmldoc/formats/options/kml-lines.xml | 2 +- xmldoc/formats/options/kml-prec.xml | 8 +-- xmldoc/formats/options/kml-rotate_colors.xml | 2 +- xmldoc/formats/options/kml-trackdirection.xml | 2 +- xmldoc/formats/options/kml-units.xml | 2 +- .../formats/options/lowranceusr-wversion.xml | 4 +- xmldoc/formats/options/magellan-maxcmts.xml | 2 +- xmldoc/formats/options/magellan1-baud.xml | 2 +- xmldoc/formats/options/magellan1-maxcmts.xml | 2 +- xmldoc/formats/options/magellan1-noack.xml | 4 +- xmldoc/formats/options/magellan1-nukewpt.xml | 2 +- xmldoc/formats/options/magellanx-maxcmts.xml | 2 +- xmldoc/formats/options/miniHomer-Bar.xml | 8 +-- xmldoc/formats/options/miniHomer-Boat.xml | 8 +-- xmldoc/formats/options/miniHomer-Car.xml | 8 +-- xmldoc/formats/options/miniHomer-Heart.xml | 8 +-- xmldoc/formats/options/miniHomer-Home.xml | 8 +-- xmldoc/formats/options/miniHomer-initbaud.xml | 2 +- .../formats/options/miniHomer-last-sector.xml | 2 +- xmldoc/formats/options/mmo-ver.xml | 4 +- xmldoc/formats/options/mtk_locus-download.xml | 4 +- .../formats/options/netstumbler-nseicon.xml | 2 +- .../formats/options/netstumbler-nsneicon.xml | 2 +- xmldoc/formats/options/netstumbler-seicon.xml | 2 +- .../formats/options/netstumbler-sneicon.xml | 2 +- .../options/nmea-append_positioning.xml | 2 +- xmldoc/formats/options/nmea-date.xml | 4 +- xmldoc/formats/options/nmea-gisteq.xml | 8 +-- xmldoc/formats/options/nmea-gpgga.xml | 4 +- xmldoc/formats/options/nmea-gpgsa.xml | 6 +- xmldoc/formats/options/nmea-gprmc.xml | 8 +-- xmldoc/formats/options/nmea-gpvtg.xml | 6 +- xmldoc/formats/options/nmea-pause.xml | 16 ++--- xmldoc/formats/options/nmea-snlen.xml | 4 +- xmldoc/formats/options/osm-created_by.xml | 2 +- xmldoc/formats/options/ozi-pack.xml | 2 +- xmldoc/formats/options/ozi-proximity.xml | 2 +- .../options/palmdoc-bookmarks_short.xml | 2 +- xmldoc/formats/options/palmdoc-dbname.xml | 2 +- xmldoc/formats/options/palmdoc-encrypt.xml | 2 +- xmldoc/formats/options/palmdoc-logs.xml | 2 +- xmldoc/formats/options/palmdoc-nosep.xml | 2 +- xmldoc/formats/options/pathaway-date.xml | 2 +- xmldoc/formats/options/saroute-controls.xml | 2 +- xmldoc/formats/options/saroute-split.xml | 2 +- xmldoc/formats/options/saroute-times.xml | 2 +- .../options/saroute-turns_important.xml | 2 +- xmldoc/formats/options/saroute-turns_only.xml | 2 +- .../options/skytraq-gps-utc-offset.xml | 2 +- .../options/skytraq-gps-week-rollover.xml | 2 +- .../formats/options/skytraq-last-sector.xml | 2 +- .../options/skytraq-targetlocation.xml | 6 +- xmldoc/formats/options/subrip-gps_date.xml | 8 +-- xmldoc/formats/options/subrip-gps_time.xml | 6 +- xmldoc/formats/options/subrip-video_time.xml | 2 +- xmldoc/formats/options/text-encrypt.xml | 2 +- xmldoc/formats/options/text-logs.xml | 2 +- xmldoc/formats/options/text-nosep.xml | 2 +- xmldoc/formats/options/text-splitoutput.xml | 2 +- xmldoc/formats/options/tpg-datum.xml | 4 +- .../formats/options/transform-rptdigits.xml | 26 +++---- xmldoc/formats/options/transform-rptname.xml | 24 +++---- xmldoc/formats/options/unicsv-datum.xml | 2 +- xmldoc/formats/options/unicsv-fields.xml | 4 +- xmldoc/formats/options/unicsv-utc.xml | 4 +- xmldoc/formats/options/xcsv-datum.xml | 2 +- xmldoc/formats/options/xcsv-style.xml | 2 +- xmldoc/formats/options/xcsv-urlbase.xml | 2 +- xmldoc/formats/ricoh.xml | 14 ++-- xmldoc/formats/s_and_t.xml | 10 +-- xmldoc/formats/saplus.xml | 6 +- xmldoc/formats/saroute.xml | 4 +- xmldoc/formats/skytraq.xml | 6 +- xmldoc/formats/sportsim.xml | 6 +- xmldoc/formats/subrip.xml | 2 +- xmldoc/formats/tabsep.xml | 2 +- xmldoc/formats/tef.xml | 6 +- xmldoc/formats/text.xml | 2 +- xmldoc/formats/tomtom.xml | 6 +- xmldoc/formats/tpg.xml | 6 +- xmldoc/formats/tpo.xml | 6 +- xmldoc/formats/tpo2.xml | 6 +- xmldoc/formats/vcard.xml | 8 +-- xmldoc/formats/wbt.xml | 12 ++-- xmldoc/formats/wintec_tes.xml | 12 ++-- xmldoc/formats/xcsv.xml | 12 ++-- 265 files changed, 813 insertions(+), 813 deletions(-) diff --git a/xmldoc/babelmain.xsl b/xmldoc/babelmain.xsl index 72bbd9788..cdac5934f 100644 --- a/xmldoc/babelmain.xsl +++ b/xmldoc/babelmain.xsl @@ -27,7 +27,7 @@ - + @@ -53,29 +53,29 @@ {block name=body}{literal} - + - + - + - + - + - + {/literal}{/block} - + diff --git a/xmldoc/filters/arc.xml b/xmldoc/filters/arc.xml index 902d35dcc..d34b45d83 100644 --- a/xmldoc/filters/arc.xml +++ b/xmldoc/filters/arc.xml @@ -1,43 +1,43 @@ - -This filter keeps or removes waypoints based on their proximity to an arc, -which is a series of connected line segments similar to a route or a track + +This filter keeps or removes waypoints based on their proximity to an arc, +which is a series of connected line segments similar to a route or a track but without any associated data other than the coordinates. Optionally, it can move each non-deleted waypoint over the closest segment of the arc. - -The arc may defined in a file whose name must be provided with the -, or the tracks or routes that have already been read. That file contains pairs of coordinates for the + +The arc may defined in a file whose name must be provided with the +, or the tracks or routes that have already been read. That file contains pairs of coordinates for the vertices of the arc, one coordinate pair per line. Comments may be -included by preceding them with a '#' character. An arc file looks +included by preceding them with a '#' character. An arc file looks something like this sample: - -# Lima Road/SR3 north of Fort Wayne, Indiana -41.150064468 -85.166207433 -41.150064468 -85.165371895 -41.149034500 -85.165157318 -41.147832870 -85.164771080 -41.146631241 -85.164384842 -41.144270897 -85.163655281 + +# Lima Road/SR3 north of Fort Wayne, Indiana +41.150064468 -85.166207433 +41.150064468 -85.165371895 +41.149034500 -85.165157318 +41.147832870 -85.164771080 +41.146631241 -85.164384842 +41.144270897 -85.163655281 41.141953468 -85.162882805 - -An arc file may optionally contain gaps in the arc. You may specify -such a gap by inserting a line containing "#break" either on a line by + +An arc file may optionally contain gaps in the arc. You may specify +such a gap by inserting a line containing "#break" either on a line by itself or after the coordinates of the starting point of the new arc segment. - + Using the arc filter -Assuming the arc above is in a file called +Assuming the arc above is in a file called lima_rd.txt, the following command line -would include only points within one mile of the section of Lima Road +would include only points within one mile of the section of Lima Road covered by the arc. gpsbabel -i geo -f 1.loc -x arc,file=lima_rd.txt,distance=1 -o mapsend -F 2.wpt - + diff --git a/xmldoc/filters/bend.xml b/xmldoc/filters/bend.xml index d6a8bfbc7..677ee2cd8 100644 --- a/xmldoc/filters/bend.xml +++ b/xmldoc/filters/bend.xml @@ -7,7 +7,7 @@ change in heading big enough. When creating a route, points are usually created inside curves or intersections. That means that, while navigating that route using a GPS unit, the course pointer would aim to the inside of that curve or -intersection, and only when you have passed that point will the GPS +intersection, and only when you have passed that point will the GPS aim to the next waypoint in the route. This behaviour is useful in marine navigation but when biking, for instance, it may be a bit late to decide where to turn to in an intersection. diff --git a/xmldoc/filters/discard.xml b/xmldoc/filters/discard.xml index 91d2c315b..e3804ea65 100644 --- a/xmldoc/filters/discard.xml +++ b/xmldoc/filters/discard.xml @@ -1,6 +1,6 @@ This filter is used to "fix" unreliable GPS data by discarding points -that are believed to be unreliable. You may specify an +that are believed to be unreliable. You may specify an HDOP and/or VDOP above a specified limit, a minimum number of satellites that must have been in view for a fix to be considered, or both. @@ -14,7 +14,7 @@ HDOP and VDOP are measures of the best possible horizontal or vertical precision -You may specify a minimum number of satellites. +You may specify a minimum number of satellites. @@ -23,4 +23,4 @@ You may specify a minimum number of satellites. Contributed by Tobias Minich and Serge Droz. - + diff --git a/xmldoc/filters/duplicate.xml b/xmldoc/filters/duplicate.xml index 2d5558d3f..46a8f09f5 100644 --- a/xmldoc/filters/duplicate.xml +++ b/xmldoc/filters/duplicate.xml @@ -1,20 +1,20 @@ - -The duplicate filter is designed to remove duplicate points based on their -short name (traditionally a waypoint's name on the GPS receiver), and/or -their location (to a precision of 6 decimals). This filter supports two -options that specify how duplicates will be recognized, - and . -Generally, at least one of these options is required. + +The duplicate filter is designed to remove duplicate points based on their +short name (traditionally a waypoint's name on the GPS receiver), and/or +their location (to a precision of 6 decimals). This filter supports two +options that specify how duplicates will be recognized, + and . +Generally, at least one of these options is required. - Using the duplicate filter to suppress points with the same + <title>Using the duplicate filter to suppress points with the same name and location This command line removes points that have duplicate short names - and duplicate locations. The result would be a - gpx file that more than likely + and duplicate locations. The result would be a + gpx file that more than likely contains only unique points and point data. gpsbabel -i gpx -f 1.gpx -f 2.gpx -x duplicate,location,shortname -o gpx -F merged_with_no_dupes.gpx - + diff --git a/xmldoc/filters/height.xml b/xmldoc/filters/height.xml index f37411cbf..549877789 100644 --- a/xmldoc/filters/height.xml +++ b/xmldoc/filters/height.xml @@ -1,12 +1,12 @@ - + The height filter allows the correction of altitude values. -At least one popular gps logger does store the ellipsoidal height (sum of the height above mean see level and the height of the geoid above the WGS84 ellipsoid) instead of the height above sea level, as it can be found on maps. +At least one popular gps logger does store the ellipsoidal height (sum of the height above mean see level and the height of the geoid above the WGS84 ellipsoid) instead of the height above sea level, as it can be found on maps. -The height filter allows for the correction of these altitude values. This filter supports two options: +The height filter allows for the correction of these altitude values. This filter supports two options: - and . -At least one of these options is required, both can be combined. + and . +At least one of these options is required, both can be combined. This option subtracts the WGS84 geoid height from every altitude. For GPS receivers like the iBlue747 the result is the height above mean see level. @@ -19,4 +19,4 @@ At least one of these options is required, both can be combined. You can specify negative numbers to subtract the value. If no unit is specified meters are assumed. For feet you can attach an "f" to the value. - + diff --git a/xmldoc/filters/interpolate.xml b/xmldoc/filters/interpolate.xml index 4814e8b4d..174d48b29 100644 --- a/xmldoc/filters/interpolate.xml +++ b/xmldoc/filters/interpolate.xml @@ -1,9 +1,9 @@ This filter modifies any tracks so that either the distance or the time between consecutive points is no more than the specified interval. Where -points are missing, the filter fills them in by following a straight +points are missing, the filter fills them in by following a straight line (actually a great circle) between the adjacent points. You -must specify either the +must specify either the or the option. @@ -27,4 +27,4 @@ trackpoints are more than 2 miles apart: gpsbabel -i gpx -f track.gpx -x interpolate,distance=2m -o gpx -F newtrack.gpx - + diff --git a/xmldoc/filters/nuketypes.xml b/xmldoc/filters/nuketypes.xml index 21e9aa8fa..4bad55ed3 100644 --- a/xmldoc/filters/nuketypes.xml +++ b/xmldoc/filters/nuketypes.xml @@ -8,9 +8,9 @@ removing all the data of any or all of those three types. If you have a GPX file that contains routes, tracks, and waypoints and you want a GPX file that contains only tracks, -you may use this filter to remove the waypoints and the routes +you may use this filter to remove the waypoints and the routes with this command: gpsbabel -i gpx -f bigfile.gpx -x nuketypes,waypoints,routes -o gpx -F tracksonly.gpx - + diff --git a/xmldoc/filters/options/arc-distance.xml b/xmldoc/filters/options/arc-distance.xml index 83a3189ec..8942edf78 100644 --- a/xmldoc/filters/options/arc-distance.xml +++ b/xmldoc/filters/options/arc-distance.xml @@ -1,9 +1,9 @@ -This option is not required, but if it is not specified the distance +This option is not required, but if it is not specified the distance defaults to zero miles, which isn't very useful. -This option specifies the maximum distance a point may be from the arc +This option specifies the maximum distance a point may be from the arc without being discarded. Points that are closer to the arc are kept, while points that are further away are discarded. diff --git a/xmldoc/filters/options/arc-exclude.xml b/xmldoc/filters/options/arc-exclude.xml index 37f84b3ba..5a5e7a10f 100644 --- a/xmldoc/filters/options/arc-exclude.xml +++ b/xmldoc/filters/options/arc-exclude.xml @@ -1,5 +1,5 @@ -When this option is specified, the usual sense of the arc filter is reversed. +When this option is specified, the usual sense of the arc filter is reversed. That is, points that are closer than distance are discarded while points that are further away are kept. diff --git a/xmldoc/filters/options/arc-file.xml b/xmldoc/filters/options/arc-file.xml index f99544aca..963bb3632 100644 --- a/xmldoc/filters/options/arc-file.xml +++ b/xmldoc/filters/options/arc-file.xml @@ -4,7 +4,7 @@ filtering. The format of the file is as described above. GPSBabel supports converting any route or track to a file usable by this -filter; simply read it in the normal way and write it using the +filter; simply read it in the normal way and write it using the arc file format. diff --git a/xmldoc/filters/options/arc-points.xml b/xmldoc/filters/options/arc-points.xml index 5f1c7d347..3a916a5eb 100644 --- a/xmldoc/filters/options/arc-points.xml +++ b/xmldoc/filters/options/arc-points.xml @@ -1,5 +1,5 @@ -When this option is specified, only points that are within the specified +When this option is specified, only points that are within the specified distance of one of the vertices of the arc are kept. This differs from the normal mode of operation in that in the normal mode, points that are close to the lines between points are also kept. diff --git a/xmldoc/filters/options/discard-elemin.xml b/xmldoc/filters/options/discard-elemin.xml index 642066b9e..6f92f86bb 100644 --- a/xmldoc/filters/options/discard-elemin.xml +++ b/xmldoc/filters/options/discard-elemin.xml @@ -1,6 +1,6 @@ -This option drops waypoints with an altitude lower than the specified -value (in meters). Although GPS altitude isn't very accurate, -GPS devices may log faulty waypoints from time to time, such as when +This option drops waypoints with an altitude lower than the specified +value (in meters). Although GPS altitude isn't very accurate, +GPS devices may log faulty waypoints from time to time, such as when near tall buildings. Elevation values that are way off may signify such waypoints. Use this option to the filter to toss known rogue points. diff --git a/xmldoc/filters/options/discard-hdop.xml b/xmldoc/filters/options/discard-hdop.xml index 8fcc16080..6310fb5d9 100644 --- a/xmldoc/filters/options/discard-hdop.xml +++ b/xmldoc/filters/options/discard-hdop.xml @@ -1,7 +1,7 @@ -This option specifies the maximum allowable Horizontal Dilution of -Precision (HDOP). By default, any point with an HDOP in excess of -this value will be discarded regardless of its VDOP, but see +This option specifies the maximum allowable Horizontal Dilution of +Precision (HDOP). By default, any point with an HDOP in excess of +this value will be discarded regardless of its VDOP, but see . diff --git a/xmldoc/filters/options/discard-hdopandvdop.xml b/xmldoc/filters/options/discard-hdopandvdop.xml index d07dd4144..97b8a463e 100644 --- a/xmldoc/filters/options/discard-hdopandvdop.xml +++ b/xmldoc/filters/options/discard-hdopandvdop.xml @@ -1,6 +1,6 @@ -If this option is used, only points that exceed both the maximum +If this option is used, only points that exceed both the maximum allowable HDOP and the maximum allowable VDOP will be discarded. This -option requires that both the and - options be specified. +option requires that both the and + options be specified. diff --git a/xmldoc/filters/options/discard-matchname.xml b/xmldoc/filters/options/discard-matchname.xml index 5073cdf0c..40e820eb9 100644 --- a/xmldoc/filters/options/discard-matchname.xml +++ b/xmldoc/filters/options/discard-matchname.xml @@ -1,5 +1,5 @@ -This option discards points that have shortnames that match the +This option discards points that have shortnames that match the provided regular expression. diff --git a/xmldoc/filters/options/discard-vdop.xml b/xmldoc/filters/options/discard-vdop.xml index f8701abd8..30aebdb28 100644 --- a/xmldoc/filters/options/discard-vdop.xml +++ b/xmldoc/filters/options/discard-vdop.xml @@ -1,7 +1,7 @@ -This option specifies the maximum allowable Vertical Dilution of -Precision (VDOP). By default, any point with an VDOP in excess of -this value will be discarded regardless of its HDOP, but see +This option specifies the maximum allowable Vertical Dilution of +Precision (VDOP). By default, any point with an VDOP in excess of +this value will be discarded regardless of its HDOP, but see . diff --git a/xmldoc/filters/options/duplicate-all.xml b/xmldoc/filters/options/duplicate-all.xml index bdbcfab60..4eaa052f9 100644 --- a/xmldoc/filters/options/duplicate-all.xml +++ b/xmldoc/filters/options/duplicate-all.xml @@ -2,13 +2,13 @@ When this option is specified, GPSBabel will remove all instances of a duplicated waypoint, not just the second and subsequent instances. If your input file contains waypoints A, B, B, and C, the output file will -contain waypoints A, B, and C without the option, +contain waypoints A, B, and C without the option, or just A and C with the option. Using the duplicate filter to implement an "ignore list." -This option may be used to implement an "ignore list." In the following +This option may be used to implement an "ignore list." In the following example, the duplicate filter is used to remove a list of waypoints to be ignored from a larger collection of waypoints: diff --git a/xmldoc/filters/options/duplicate-correct.xml b/xmldoc/filters/options/duplicate-correct.xml index 8faefd587..a1d809700 100644 --- a/xmldoc/filters/options/duplicate-correct.xml +++ b/xmldoc/filters/options/duplicate-correct.xml @@ -1,11 +1,11 @@ -This option is used to change the locations of waypoints without losing any -of the other associated information. When this option is specified, the +This option is used to change the locations of waypoints without losing any +of the other associated information. When this option is specified, the latitude and longitude from later duplicates will replace the latitude and longitude in the original waypoint. -As an example, this option may be used to adjust the locations of "puzzle" +As an example, this option may be used to adjust the locations of "puzzle" geocaches in a Groundspeak pocket query: @@ -13,9 +13,9 @@ geocaches in a Groundspeak pocket query: geocaches gpsbabel -i gpx -f 43622.gpx -i csv -f corrections.csv -x duplicate,shortname,correct -o gpx -F 43622-corrected.gpx -After this command is run, the waypoints in the output file will have all -of the descriptive information from 43622.gpx, but -waypoints that were also found in corrections.csv +After this command is run, the waypoints in the output file will have all +of the descriptive information from 43622.gpx, but +waypoints that were also found in corrections.csv will have their coordinates replaced with the coordinates from that file. diff --git a/xmldoc/filters/options/duplicate-location.xml b/xmldoc/filters/options/duplicate-location.xml index 910bfc30c..67b040ba6 100644 --- a/xmldoc/filters/options/duplicate-location.xml +++ b/xmldoc/filters/options/duplicate-location.xml @@ -1,9 +1,9 @@ -This option causes the duplicate filter to remove any additional waypoint -that has the same coordinates (to six decimal degrees) as a waypoint that -came before. This option may be used to remove duplicate waypoints if the +This option causes the duplicate filter to remove any additional waypoint +that has the same coordinates (to six decimal degrees) as a waypoint that +came before. This option may be used to remove duplicate waypoints if the names are not expected to be the same. It also might be used along with the - option to remove duplicate waypoints if the names + option to remove duplicate waypoints if the names of several unrelated groups of waypoints might be the same. diff --git a/xmldoc/filters/options/duplicate-shortname.xml b/xmldoc/filters/options/duplicate-shortname.xml index 72f88c2fc..d24ff392b 100644 --- a/xmldoc/filters/options/duplicate-shortname.xml +++ b/xmldoc/filters/options/duplicate-shortname.xml @@ -1,8 +1,8 @@ -This option is the one most often used with the duplicate filter. This +This option is the one most often used with the duplicate filter. This option instructs the duplicate filter to remove any waypoints that share a short name with a waypoint that has come before. This option might be -used to remove duplicates if you are merging two datasets that were +used to remove duplicates if you are merging two datasets that were each created in part from a common ancestor dataset. diff --git a/xmldoc/filters/options/interpolate-route.xml b/xmldoc/filters/options/interpolate-route.xml index 1605b9f6c..e79e2e193 100644 --- a/xmldoc/filters/options/interpolate-route.xml +++ b/xmldoc/filters/options/interpolate-route.xml @@ -1,5 +1,5 @@ -If this option is specified, the interpolate filter interpolates routes +If this option is specified, the interpolate filter interpolates routes rather than tracks. Because route points do not have time stamps, it is an error to use this option with the option. diff --git a/xmldoc/filters/options/nuketypes-waypoints.xml b/xmldoc/filters/options/nuketypes-waypoints.xml index 26c71901e..00edd4bd2 100644 --- a/xmldoc/filters/options/nuketypes-waypoints.xml +++ b/xmldoc/filters/options/nuketypes-waypoints.xml @@ -1,5 +1,5 @@ -This option causes the nuketypes filter to discard all waypoints that are not +This option causes the nuketypes filter to discard all waypoints that are not associated with a track or route. diff --git a/xmldoc/filters/options/polygon-exclude.xml b/xmldoc/filters/options/polygon-exclude.xml index 6a68bdfa2..cce1cd82f 100644 --- a/xmldoc/filters/options/polygon-exclude.xml +++ b/xmldoc/filters/options/polygon-exclude.xml @@ -1,5 +1,5 @@ -When this option is specified, the usual sense of the polygon filter is +When this option is specified, the usual sense of the polygon filter is reversed. That is, points that are inside the polygon are discarded while points that are further away are kept. diff --git a/xmldoc/filters/options/polygon-file.xml b/xmldoc/filters/options/polygon-file.xml index 032b595c1..31a967c28 100644 --- a/xmldoc/filters/options/polygon-file.xml +++ b/xmldoc/filters/options/polygon-file.xml @@ -7,9 +7,9 @@ filtering. The format of the file is as described above. GPSBabel supports converting any route or track to a file usable by this -filter; simply read it in the normal way and write it using the -arc file format. Afterward, you will -need to make sure that the first point and the last point in the +filter; simply read it in the normal way and write it using the +arc file format. Afterward, you will +need to make sure that the first point and the last point in the file are the same, as the polygon filter depends on that. You can do so with any text editor. diff --git a/xmldoc/filters/options/position-distance.xml b/xmldoc/filters/options/position-distance.xml index ebd18d5d9..d85b1762a 100644 --- a/xmldoc/filters/options/position-distance.xml +++ b/xmldoc/filters/options/position-distance.xml @@ -1,9 +1,9 @@ -This option specifies the minimum allowable distance between two points. If +This option specifies the minimum allowable distance between two points. If two points are closer than this distance, only one of them is kept. -Distances may be expressed in feet (30f) or meters (10m). If no unit is +Distances may be expressed in feet (30f) or meters (10m). If no unit is specified, the distance is assumed to be in feet. diff --git a/xmldoc/filters/options/position-time.xml b/xmldoc/filters/options/position-time.xml index b12bee718..394cda286 100644 --- a/xmldoc/filters/options/position-time.xml +++ b/xmldoc/filters/options/position-time.xml @@ -1,6 +1,6 @@ - Specifies the maximum time in seconds between any two points. If the - time difference is larger than what's specified here, the points will + Specifies the maximum time in seconds between any two points. If the + time difference is larger than what's specified here, the points will not be discarded. diff --git a/xmldoc/filters/options/radius-asroute.xml b/xmldoc/filters/options/radius-asroute.xml index 4cd6539f9..aff16e2be 100644 --- a/xmldoc/filters/options/radius-asroute.xml +++ b/xmldoc/filters/options/radius-asroute.xml @@ -5,8 +5,8 @@ The order of points in the route is by distance from the center (unless the option is also specified.) -Note that this route is not necessarily the most efficient route to visit -all of the points. In fact, for some data sets, it might be the least +Note that this route is not necessarily the most efficient route to visit +all of the points. In fact, for some data sets, it might be the least efficient route. diff --git a/xmldoc/filters/options/radius-distance.xml b/xmldoc/filters/options/radius-distance.xml index 7e4ff8212..3b4d950c5 100644 --- a/xmldoc/filters/options/radius-distance.xml +++ b/xmldoc/filters/options/radius-distance.xml @@ -4,7 +4,7 @@ This option is required. This option specifies the maximum distance a point may be from the central point in order to remain in the dataset. Points closer than this distance -will be kept and points further away will be removed (unless the +will be kept and points further away will be removed (unless the option is specified.) diff --git a/xmldoc/filters/options/radius-maxcount.xml b/xmldoc/filters/options/radius-maxcount.xml index 2ca05844d..1a228e08a 100644 --- a/xmldoc/filters/options/radius-maxcount.xml +++ b/xmldoc/filters/options/radius-maxcount.xml @@ -1,22 +1,22 @@ This option specifies the maximum number of points that the radius filter may -keep. If there are more than this number of points within the specified +keep. If there are more than this number of points within the specified distance of the center, the more distant points will be discarded even though -they are within the specified distance. If this option is not specified, +they are within the specified distance. If this option is not specified, all points are kept regardless of how many there are. -Note that if the option is also specified, this +Note that if the option is also specified, this option will instead keep points based on their position within the input file rather than on their distance from the center. This may or may not be what you want. -Note, too, that this option may be used with the -option, but the results might not be what you expect. In particular, the -results will not be the same as if you had kept all of the points you'd -otherwise throw away. You will still get no more than -maxcount points, but they will all be at least +Note, too, that this option may be used with the +option, but the results might not be what you expect. In particular, the +results will not be the same as if you had kept all of the points you'd +otherwise throw away. You will still get no more than +maxcount points, but they will all be at least distance away from the center. (And possibly sorted.) - + diff --git a/xmldoc/filters/options/simplify-count.xml b/xmldoc/filters/options/simplify-count.xml index 9b268a3c9..3aa750cef 100644 --- a/xmldoc/filters/options/simplify-count.xml +++ b/xmldoc/filters/options/simplify-count.xml @@ -1,7 +1,7 @@ This option specifies the maximum number of points which may appear in the simplified route. For example, if you specify "count=50", all resulting -routes will contain 50 points or fewer. +routes will contain 50 points or fewer. You must specify either this option or the option. diff --git a/xmldoc/filters/options/simplify-crosstrack.xml b/xmldoc/filters/options/simplify-crosstrack.xml index 3b3c2831e..eb7600f0c 100644 --- a/xmldoc/filters/options/simplify-crosstrack.xml +++ b/xmldoc/filters/options/simplify-crosstrack.xml @@ -1,7 +1,7 @@ -This option instructs GPSBabel to remove points that have the smallest +This option instructs GPSBabel to remove points that have the smallest overall effect on the overall shape of the route. Using this method, the -first point to be removed will be the one that is closest to a line drawn +first point to be removed will be the one that is closest to a line drawn between the two points adjacent to it. diff --git a/xmldoc/filters/options/simplify-error.xml b/xmldoc/filters/options/simplify-error.xml index 0e1963874..4e6a18417 100644 --- a/xmldoc/filters/options/simplify-error.xml +++ b/xmldoc/filters/options/simplify-error.xml @@ -2,11 +2,11 @@ This option specifies the maximum allowable error that may be introduced by removing a single point. Used with the and methods, the value of this option is a distance, -specified in miles by default. You may also specify the distance in +specified in miles by default. You may also specify the distance in kilometers by adding a 'k' to the end of the number. For the method it is a dimensionless quantity. - + How the error is determined depends on whether the , , or method is used. If you are using the length method, the error is the change in the length of diff --git a/xmldoc/filters/options/simplify-length.xml b/xmldoc/filters/options/simplify-length.xml index 0842f2f1f..ccfdf8305 100644 --- a/xmldoc/filters/options/simplify-length.xml +++ b/xmldoc/filters/options/simplify-length.xml @@ -1,4 +1,4 @@ This option instructs GPSBabel to simplify by removing points that cause the -smallest change in the overall length of the route first. +smallest change in the overall length of the route first. diff --git a/xmldoc/filters/options/stack-append.xml b/xmldoc/filters/options/stack-append.xml index eb4299e05..65a197e18 100644 --- a/xmldoc/filters/options/stack-append.xml +++ b/xmldoc/filters/options/stack-append.xml @@ -1,5 +1,5 @@ -This option is only valid in conjunction with the . +This option is only valid in conjunction with the . When it is specified, the topmost collection of data from the stack is appended to the current collection of data. diff --git a/xmldoc/filters/options/stack-copy.xml b/xmldoc/filters/options/stack-copy.xml index ae9fe8449..8797b9b0b 100644 --- a/xmldoc/filters/options/stack-copy.xml +++ b/xmldoc/filters/options/stack-copy.xml @@ -1,6 +1,6 @@ This option is only valid when used with the option. -When this option is specified, a copy of the current state is pushed onto -the stack but the current state is left unchanged. Otherwise, the push +When this option is specified, a copy of the current state is pushed onto +the stack but the current state is left unchanged. Otherwise, the push operation clears the current data collection. diff --git a/xmldoc/filters/options/stack-pop.xml b/xmldoc/filters/options/stack-pop.xml index 0bfb71660..446712393 100644 --- a/xmldoc/filters/options/stack-pop.xml +++ b/xmldoc/filters/options/stack-pop.xml @@ -2,8 +2,8 @@ This is one of three "primary" options to the stack filter. -This option "pops" the collection of data from the top of the stack. -By default, the saved state replaces the current state, but see the - and options for +This option "pops" the collection of data from the top of the stack. +By default, the saved state replaces the current state, but see the + and options for alternatives. diff --git a/xmldoc/filters/options/stack-push.xml b/xmldoc/filters/options/stack-push.xml index 8f76ad567..e149ca103 100644 --- a/xmldoc/filters/options/stack-push.xml +++ b/xmldoc/filters/options/stack-push.xml @@ -3,6 +3,6 @@ This is one of three "primary" options to the stack filter. When this option is specified, the current state is pushed onto the top of -the stack. By default, the current state is then cleared, but the +the stack. By default, the current state is then cleared, but the option can be used to cause it to be saved. diff --git a/xmldoc/filters/options/stack-replace.xml b/xmldoc/filters/options/stack-replace.xml index 2e967fdba..59bcefe2e 100644 --- a/xmldoc/filters/options/stack-replace.xml +++ b/xmldoc/filters/options/stack-replace.xml @@ -1,8 +1,8 @@ This option is only valid when used with the option. -This is the default behavior of the option, so you -should never need to specify it, but it is included for the sake of -readability. When this option is specified, the popped state replaces +This is the default behavior of the option, so you +should never need to specify it, but it is included for the sake of +readability. When this option is specified, the popped state replaces the current state. diff --git a/xmldoc/filters/options/track-course.xml b/xmldoc/filters/options/track-course.xml index 36b83f29a..1de9c41ea 100644 --- a/xmldoc/filters/options/track-course.xml +++ b/xmldoc/filters/options/track-course.xml @@ -1,7 +1,7 @@ -This option computes (or recomputes) a value for the GPS heading at each -trackpoint. This is most useful with trackpoints from formats that don't -support heading information or for trackpoints synthesized by the +This option computes (or recomputes) a value for the GPS heading at each +trackpoint. This is most useful with trackpoints from formats that don't +support heading information or for trackpoints synthesized by the interpolate filter. The heading at each trackpoint is simply the course from the previous trackpoint in the track. The first trackpoint in each track diff --git a/xmldoc/filters/options/track-discard.xml b/xmldoc/filters/options/track-discard.xml index c654609da..a77b79dad 100644 --- a/xmldoc/filters/options/track-discard.xml +++ b/xmldoc/filters/options/track-discard.xml @@ -1,10 +1,10 @@ - + This option is used in conjunction with the merge option to discard track points with missing timestamps instead of aborting with the "Found track point at lat,lon without time!" error. Merging tracks with missing timestamps with the track filter - + Suppose you want to merge tracks that may have missing timestamps. To do that, use this command line: gpsbabel -t -i gpx -f john.gpx -f doe.gpx -x track,merge,discard -o gpx -F john_doe.gpx diff --git a/xmldoc/filters/options/track-fix.xml b/xmldoc/filters/options/track-fix.xml index 4cd9f303a..7b843b4de 100644 --- a/xmldoc/filters/options/track-fix.xml +++ b/xmldoc/filters/options/track-fix.xml @@ -3,7 +3,7 @@ This option sets the GPS fix status for all trackpoints to the specified value. Valid values for this option are PPS, DGPS, 3D, 2D, or NONE. -This option is most useful when converting from a format that doesn't +This option is most useful when converting from a format that doesn't contain GPS fix status to one that requires it. diff --git a/xmldoc/filters/options/track-merge.xml b/xmldoc/filters/options/track-merge.xml index 0d7ea30d2..7b9e4ceb2 100644 --- a/xmldoc/filters/options/track-merge.xml +++ b/xmldoc/filters/options/track-merge.xml @@ -1,11 +1,11 @@ - -This option puts all track points from all tracks into a single track + +This option puts all track points from all tracks into a single track and sorts them by time stamp. Redundant points with identical time stamps will be dropped. Merging tracks with the track filter - -Suppose you want to merge tracks recorded with two different GPS devices + +Suppose you want to merge tracks recorded with two different GPS devices at the same time. To do that, use this command line: gpsbabel -t -i gpx -f john.gpx -i gpx -f doe.gpx -x track,merge,title="COMBINED LOG" -o gpx -F john_doe.gpx diff --git a/xmldoc/filters/options/track-minimum_points.xml b/xmldoc/filters/options/track-minimum_points.xml index 31b79a929..bf572a4e3 100644 --- a/xmldoc/filters/options/track-minimum_points.xml +++ b/xmldoc/filters/options/track-minimum_points.xml @@ -3,6 +3,6 @@ Eliminates any remaining tracks with fewer than this number of trackpoints. This step is performed last by this filter and is used to clean up earlier -simplifications that may have left tracks with so few points as to be +simplifications that may have left tracks with so few points as to be useless, such as a track taken while stationary but with GPS wander. diff --git a/xmldoc/filters/options/track-pack.xml b/xmldoc/filters/options/track-pack.xml index c65f6893f..ae609adbe 100644 --- a/xmldoc/filters/options/track-pack.xml +++ b/xmldoc/filters/options/track-pack.xml @@ -1,7 +1,7 @@ - + This option causes all tracks to be appended to one another to form a single track. This option does not work if any two tracks overlap in time; in that -case, consider using the option. +case, consider using the option. This option is most useful for rejoining tracks that might have diff --git a/xmldoc/filters/options/track-sdistance.xml b/xmldoc/filters/options/track-sdistance.xml index 65a40ae68..89060b6ea 100644 --- a/xmldoc/filters/options/track-sdistance.xml +++ b/xmldoc/filters/options/track-sdistance.xml @@ -3,33 +3,33 @@ is greater than the distance given as a parameter. The distance must be numeric and can be in miles or kilometers, expressed as one of the character "k", or "m". - If sdistance is given no parameters, this option has the same - effect as the split option without parameters. If there is more + If sdistance is given no parameters, this option has the same + effect as the split option without parameters. If there is more than one track, use the pack option before before using this. For example, to split the track if the distance between points is greater than 100 meters, use this: -gpsbabel -t - -i gpx -f in.gpx - -x track,pack,sdistance=0.1k" +gpsbabel -t + -i gpx -f in.gpx + -x track,pack,sdistance=0.1k" -o gpx -F out.gpx The sdistance option can be combined with the split option. The track then will be split only if both time and distance - interval exceeds the supplied values. This technique can be used to + interval exceeds the supplied values. This technique can be used to filter out gaps from the tracklog. The gap is kept only if the gps device is without - signal for longer time than that given and during that time it moves + signal for longer time than that given and during that time it moves a distance over that given. This example splits the track if the device is without signal for at least 5 minutes and during this time moves more than 300 meters: -gpsbabel -t - -i gpx -f in.gpx - -x track,pack,sdistance=0.3k,split=5m +gpsbabel -t + -i gpx -f in.gpx + -x track,pack,sdistance=0.3k,split=5m -o gpx -F out.gpx diff --git a/xmldoc/filters/options/track-speed.xml b/xmldoc/filters/options/track-speed.xml index 2cf43b396..f9af5fda4 100644 --- a/xmldoc/filters/options/track-speed.xml +++ b/xmldoc/filters/options/track-speed.xml @@ -1,12 +1,12 @@ This option computes a value for the GPS speed at each trackpoint. This is most useful with trackpoints from formats that don't support -speed information or for trackpoints synthesized by the +speed information or for trackpoints synthesized by the interpolate filter. The speed at each trackpoint is the average speed from the -previous trackpoint (distance divided by time). The first trackpoint +previous trackpoint (distance divided by time). The first trackpoint in each track is assigned a speed of "unknown." diff --git a/xmldoc/filters/options/track-split.xml b/xmldoc/filters/options/track-split.xml index d096bc52e..79a3e233c 100644 --- a/xmldoc/filters/options/track-split.xml +++ b/xmldoc/filters/options/track-split.xml @@ -7,8 +7,8 @@ gpsbabel -t -i gpx -f in.gpx -x track,split,title="ACTIVE LOG # %Y%m%d" -o gpx -F out.gpx If the input has multiple tracks, pack them together before splitting them back apart per day thusly: - gpsbabel -t -i gpx -f in.gpx - -x track,pack,split,title="ACTIVE LOG # %D" + gpsbabel -t -i gpx -f in.gpx + -x track,pack,split,title="ACTIVE LOG # %D" -o gpx -F out.gpx Additionally you can add an interval to the split option. With this the track will be split if the time @@ -19,9 +19,9 @@ splitting them back apart per day thusly: For example, to split a track based on an four hour interval, use this: - -gpsbabel -t - -i gpx -f in.gpx - -x track,pack,split=4h,title="LOG # %c" + +gpsbabel -t + -i gpx -f in.gpx + -x track,pack,split=4h,title="LOG # %c" -o gpx -F out.gpx diff --git a/xmldoc/filters/options/track-start.xml b/xmldoc/filters/options/track-start.xml index 143e05d22..0ead2bd56 100644 --- a/xmldoc/filters/options/track-start.xml +++ b/xmldoc/filters/options/track-start.xml @@ -1,16 +1,16 @@ -This option is used along with the to discard -trackpoints that were recorded outside of a specific period of time. +This option is used along with the to discard +trackpoints that were recorded outside of a specific period of time. This option specifies the beginning of the time period. If this option is not specified, the time period is assumed to begin at the -dawn of time or January 1, 1970, whichever was later. The time for this -option is expressed in UTC. +dawn of time or January 1, 1970, whichever was later. The time for this +option is expressed in UTC. The value of this option must be in the form of YYYYMMDDHHMMSS, but it is -not necessary to specify the smaller time units if they are not needed. +not necessary to specify the smaller time units if they are not needed. That is, if you only care about points logged between 10 AM and 6 PM on a given date, you need not specify the minutes or seconds. @@ -19,6 +19,6 @@ given date, you need not specify the minutes or seconds. To get only the parts of a track that were mapped on 20 July 2005 between 10 AM and 6 PM, use this command line: - + gpsbabel -t -i gpx -f in.gpx -x track,start=2005072010,stop=2005072018 -o gpx -F out.gpx diff --git a/xmldoc/filters/options/track-stop.xml b/xmldoc/filters/options/track-stop.xml index a86755aeb..4ec4b09eb 100644 --- a/xmldoc/filters/options/track-stop.xml +++ b/xmldoc/filters/options/track-stop.xml @@ -1,15 +1,15 @@ -This option is used in conjunction with the option to -discard all trackpoints outside of a given period of time. This option +This option is used in conjunction with the option to +discard all trackpoints outside of a given period of time. This option defines the end of the time period. -If this option is not specified, the time period is assumed to end at the +If this option is not specified, the time period is assumed to end at the end of civilization as we know it or the year 2038, whichever comes first. The time for this option is expressed in UTC. -See the option for the format of this value and an +See the option for the format of this value and an example of usage. diff --git a/xmldoc/filters/options/track-title.xml b/xmldoc/filters/options/track-title.xml index be578bd46..6ea16f495 100644 --- a/xmldoc/filters/options/track-title.xml +++ b/xmldoc/filters/options/track-title.xml @@ -1,10 +1,10 @@ - + This option specifies a title for tracks generated by the track filter. -By default, the title of the new track is composed of the start time of +By default, the title of the new track is composed of the start time of the track appended to this value. -If this value contains a percent (%) character, it is treated as a format -string for the POSIX strftime function, allowing custom time-based -track names. +If this value contains a percent (%) character, it is treated as a format +string for the POSIX strftime function, allowing custom time-based +track names. diff --git a/xmldoc/filters/options/transform-del.xml b/xmldoc/filters/options/transform-del.xml index 75a82fa12..aceaf77fa 100644 --- a/xmldoc/filters/options/transform-del.xml +++ b/xmldoc/filters/options/transform-del.xml @@ -1,6 +1,6 @@ This option, when used in connection with the wpt, rte, or trk options, tells -GPSBabel to delete the source data after conversion. This is most useful if +GPSBabel to delete the source data after conversion. This is most useful if you are trying to avoid duplicated data in the output. diff --git a/xmldoc/filters/options/transform-rptname.xml b/xmldoc/filters/options/transform-rptname.xml index 29e66831b..4df5c9257 100644 --- a/xmldoc/filters/options/transform-rptname.xml +++ b/xmldoc/filters/options/transform-rptname.xml @@ -1,12 +1,12 @@ - -With this option you can decide to let GPSBabel name generated route points according to their source track name. - - -GPSBabel creates route points during the transformation process named "RPTnnn" where nnn is a numeric part. - -Using this option GPSBabel can be configured to replace the "RPT" part of the generated names by the name of the source track during the transformation process. This is especially usefull if several differently named tracks are contained in the source file which should each be transformed into routes. - - -Convert a GPX track to a GPX route, deleting the original track, naming the generated points like the original track name. -gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptname=y -o gpx -F route.gpx - + +With this option you can decide to let GPSBabel name generated route points according to their source track name. + + +GPSBabel creates route points during the transformation process named "RPTnnn" where nnn is a numeric part. + +Using this option GPSBabel can be configured to replace the "RPT" part of the generated names by the name of the source track during the transformation process. This is especially usefull if several differently named tracks are contained in the source file which should each be transformed into routes. + + +Convert a GPX track to a GPX route, deleting the original track, naming the generated points like the original track name. +gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptname=y -o gpx -F route.gpx + diff --git a/xmldoc/filters/options/transform-rte.xml b/xmldoc/filters/options/transform-rte.xml index 08ff8b48a..85986c2a9 100644 --- a/xmldoc/filters/options/transform-rte.xml +++ b/xmldoc/filters/options/transform-rte.xml @@ -4,7 +4,7 @@ This option selects the destination type of this filter to be routes. Choose th Converting a pile of waypoints to a GPX route -Say you you have a data file that came from CSV file that you want to convert +Say you you have a data file that came from CSV file that you want to convert to a GPX route that can be loaded into Basecamp. Use the following command: gpsbabel -i csv -f blah.txt -x transform,rte=wpt -o gdb -F blah.gdb diff --git a/xmldoc/filters/options/transform-trk.xml b/xmldoc/filters/options/transform-trk.xml index 99b1c8a57..3f5475977 100644 --- a/xmldoc/filters/options/transform-trk.xml +++ b/xmldoc/filters/options/transform-trk.xml @@ -1,12 +1,12 @@ -This option selects the destination type of this filter to be tracks. -Choose this when you want to create tracks from a list of waypoints or routes. +This option selects the destination type of this filter to be tracks. +Choose this when you want to create tracks from a list of waypoints or routes. A single track will be created in the sequence they appear in the input. Converting a pile of waypoints to a GPX track -Say you you have a data file that came from CSV file that you want to convert +Say you you have a data file that came from CSV file that you want to convert to a GPX track that can be loaded into Basecamp. Use the following command: gpsbabel -i csv -f blah.txt -x transform,trk=wpt -o gdb -F blah.gdb diff --git a/xmldoc/filters/options/transform-wpt.xml b/xmldoc/filters/options/transform-wpt.xml index 513b5ef07..45c9f0a88 100644 --- a/xmldoc/filters/options/transform-wpt.xml +++ b/xmldoc/filters/options/transform-wpt.xml @@ -1,5 +1,5 @@ -This option selects the destination type of this filter to be waypoints. +This option selects the destination type of this filter to be waypoints. Choose this when you want to convert tracks or routes into waypoints. diff --git a/xmldoc/filters/options/validate-debug.xml b/xmldoc/filters/options/validate-debug.xml index c741e026f..550bd7dc3 100644 --- a/xmldoc/filters/options/validate-debug.xml +++ b/xmldoc/filters/options/validate-debug.xml @@ -1,3 +1,3 @@ -This option will output verbose messages reporting the state of the internal data structures holding waypoints, routes and tracks. Detected problems will normally produce a fatal error, but with this option in effect no error will be thrown allowing continued processing. +This option will output verbose messages reporting the state of the internal data structures holding waypoints, routes and tracks. Detected problems will normally produce a fatal error, but with this option in effect no error will be thrown allowing continued processing. diff --git a/xmldoc/filters/polygon.xml b/xmldoc/filters/polygon.xml index ddf2699f6..d36012061 100644 --- a/xmldoc/filters/polygon.xml +++ b/xmldoc/filters/polygon.xml @@ -1,6 +1,6 @@ - + The polygon filter includes points if they are inside -of a polygon. A polygon file looks like an +of a polygon. A polygon file looks like an arc file, except that the arc it describes must be a closed cycle. That is, for a simple polygon, the first and last points must be the @@ -14,7 +14,7 @@ same. Here's a square: 42.0000 -85.0000 41.0000 -85.0000 - + Polygons may include islands and holes. To include an island or a hole, just append it to the main polygon. @@ -34,44 +34,44 @@ island or a hole, just append it to the main polygon. As with the arc filter, you define a polygon by giving the name of the file that contains it, using -the option. +the option. - + Note that this filter currently will not work properly if your polygon contains one or both poles or if it spans the line of 180 degrees east or west longitude. Using the polygon filter - -Suppose you have a polygon file that defines the border of your county, -called mycounty.txt. This command line will give you only the points + +Suppose you have a polygon file that defines the border of your county, +called mycounty.txt. This command line will give you only the points in your county: gpsbabel -i geo -f 1.loc -x polygon,file=mycounty.txt -o mapsend -F 2.wpt -Using the polygon and arc filters to find points in or nearly in a +<title>Using the polygon and arc filters to find points in or nearly in a polygon Because the polygon and arc filters use the same file format, you can use them together to find all points that are -"in or nearly in" a polygon. This can be useful if your waypoints or the -boundaries of your polygon are not quite perfect, so you want to provide a -buffer zone around it in case there are points nearby that should be in the +"in or nearly in" a polygon. This can be useful if your waypoints or the +boundaries of your polygon are not quite perfect, so you want to provide a +buffer zone around it in case there are points nearby that should be in the polygon but aren't quite. -gpsbabel -i gpx -f points.gpx -x stack,push -x polygon,file=mycounty.txt --x stack,swap -x arc,file=mycounty.txt,distance=1k -x stack,pop,append +gpsbabel -i gpx -f points.gpx -x stack,push -x polygon,file=mycounty.txt +-x stack,swap -x arc,file=mycounty.txt,distance=1k -x stack,pop,append -x duplicate,shortname -o gpx -F nearmycounty.gpx This command makes a copy of the points, finds the ones that are in your your county, swaps that result with the copy of the original set of points, -finds the ones from that set that are within 1 km of the border of the county, +finds the ones from that set that are within 1 km of the border of the county, puts the two lists together, and then filters out any points that appear twice -(This step is necessary because points inside the county but near the county +(This step is necessary because points inside the county but near the county line will be kept by both the polygon and the arc filter.) diff --git a/xmldoc/filters/position.xml b/xmldoc/filters/position.xml index c6b957179..e66450b70 100644 --- a/xmldoc/filters/position.xml +++ b/xmldoc/filters/position.xml @@ -1,4 +1,4 @@ - + This filter removes points based on their proximity to each other. For waypoints a point is removed if it is within the specified distance of a preceeding point. For routes and tracks consecutive points are removed until the distance between the bracketing points is greater than the specified distance. @@ -7,9 +7,9 @@ For routes and tracks consecutive points are removed until the distance between Using the position filter to suppress close points -The following command removes multiple points that are within +The following command removes multiple points that are within one foot of each other, leaving just one. gpsbabel -i geo -f 1.loc -f 2.loc -x position,distance=1f -o mapsend -F 3.wpt - + diff --git a/xmldoc/filters/radius.xml b/xmldoc/filters/radius.xml index 1e3f4ffd7..c2fbda597 100644 --- a/xmldoc/filters/radius.xml +++ b/xmldoc/filters/radius.xml @@ -1,10 +1,10 @@ - -This filter includes or excludes waypoints based on their proximity to a -central point. All waypoints more than the specified distance from the + +This filter includes or excludes waypoints based on their proximity to a +central point. All waypoints more than the specified distance from the specified point will be removed from the dataset. -By default, all remaining points are sorted so that points closer to the +By default, all remaining points are sorted so that points closer to the center appear earlier in the output file. @@ -14,4 +14,4 @@ center appear earlier in the output file. gpsbabel -i geo -f 1.loc -x radius,distance=1.5M,lat=30.0,lon=-90.0 -o mapsend -F 2.wpt - + diff --git a/xmldoc/filters/reverse.xml b/xmldoc/filters/reverse.xml index afdb116ed..7fb303868 100644 --- a/xmldoc/filters/reverse.xml +++ b/xmldoc/filters/reverse.xml @@ -1,5 +1,5 @@ - + The reverse filter is used to reverse tracks and routes. It's mostly useful for those few formats where track/route sequence matters and there isn't a way to reverse them using @@ -16,4 +16,4 @@ will be in for unpleasant ride. application cares about timestamps - + diff --git a/xmldoc/filters/simplify.xml b/xmldoc/filters/simplify.xml index 026551bc0..7502254a2 100644 --- a/xmldoc/filters/simplify.xml +++ b/xmldoc/filters/simplify.xml @@ -1,21 +1,21 @@ - -The Simplify filter is used to simplify routes and tracks for use with -formats that limit the number of points they can contain or just to + +The Simplify filter is used to simplify routes and tracks for use with +formats that limit the number of points they can contain or just to reduce the complexity of a route. -The filter attempts to remove points from each route until the number -of points or the error is within the given bounds, while also attempting -to preserve the shape of the original route as much as possible. +The filter attempts to remove points from each route until the number +of points or the error is within the given bounds, while also attempting +to preserve the shape of the original route as much as possible. - -The quality of the results will vary depending on the density of points + +The quality of the results will vary depending on the density of points in the original route and the length of the original route. - -For example, suppose you have a route from Street Atlas 2003 that you -wish to use with a Magellan GPS receiver that only supports up to 50 points + +For example, suppose you have a route from Street Atlas 2003 that you +wish to use with a Magellan GPS receiver that only supports up to 50 points in a route: gpsbabel -r -i saroute -f RoadTrip.anr -x simplify,count=50 -o magellan -F grocery.rte - + diff --git a/xmldoc/filters/sort.xml b/xmldoc/filters/sort.xml index f6af2dc60..7541be0af 100644 --- a/xmldoc/filters/sort.xml +++ b/xmldoc/filters/sort.xml @@ -1,4 +1,4 @@ This filter sorts waypoints, routes and/or tracks by the selected field(s). - + diff --git a/xmldoc/filters/stack.xml b/xmldoc/filters/stack.xml index 833012355..8760429aa 100644 --- a/xmldoc/filters/stack.xml +++ b/xmldoc/filters/stack.xml @@ -1,6 +1,6 @@ - -This filter is designed to solve advanced problems that involve shuffling -multiple lists of waypoints, tracks, or routes. + +This filter is designed to solve advanced problems that involve shuffling +multiple lists of waypoints, tracks, or routes. The stack filter can be used to save the current state of the entire @@ -8,7 +8,7 @@ collection of data. That state is placed on top of a stack of collections, so you can simultaneously have as many stored collections of data as you can fit in your computer's memory. - + The stack filter can be used in conjunction with other filters to implement a "union" or "logical or" functionality. The basic idea is to use the stack to store copies of the @@ -21,13 +21,13 @@ can fit in your computer's memory. duplicates can be removed with the DUPLICATE filter; see above.) - -gpsbabel -i gpx -f in.gpx - -x stack,push,copy - -x polygon,file=county_a.txt - -x stack,swap - -x polygon,file=county_b.txt - -x stack,pop,append + +gpsbabel -i gpx -f in.gpx + -x stack,push,copy + -x polygon,file=county_a.txt + -x stack,swap + -x polygon,file=county_b.txt + -x stack,pop,append -o gpx -F out.gpx This example reads a large list of waypoints and @@ -35,15 +35,15 @@ gpsbabel -i gpx -f in.gpx writing the waypoint descriptions into two different PalmDoc files and exporting all of the points to the GPS receiver: - -gpsbabel -i gpx -f indiana.gpx - -x stack,push,copy - -x radius,lat=41.0765,lon=-85.1365,distance=20m - -o palmdoc,dbname=Fort\ Wayne -F fortwayne.pdb - -x stack,swap - -x radius,lat=39.7733,lon=-86.1433,distance=20m - -o palmdoc,dbname=Indianapolis -F indianapolis.pdb - -x stack,pop,append + +gpsbabel -i gpx -f indiana.gpx + -x stack,push,copy + -x radius,lat=41.0765,lon=-85.1365,distance=20m + -o palmdoc,dbname=Fort\ Wayne -F fortwayne.pdb + -x stack,swap + -x radius,lat=39.7733,lon=-86.1433,distance=20m + -o palmdoc,dbname=Indianapolis -F indianapolis.pdb + -x stack,pop,append -o magellan -F fwaind.wpt - + diff --git a/xmldoc/filters/track.xml b/xmldoc/filters/track.xml index cf6c39494..e2177de75 100644 --- a/xmldoc/filters/track.xml +++ b/xmldoc/filters/track.xml @@ -5,4 +5,4 @@ WARNING: This filter always drops empty tracks. This filter performs various operations on track data. - + diff --git a/xmldoc/formats/arc.xml b/xmldoc/formats/arc.xml index 4365cce28..de22f2358 100644 --- a/xmldoc/formats/arc.xml +++ b/xmldoc/formats/arc.xml @@ -1,14 +1,14 @@ -This format is used by GPSBabel itself as the input to the -arc and +This format is used by GPSBabel itself as the input to the +arc and polygon filters. See those filters for more information. -The arc format reads two numeric fields, a latitude and a longitude, -in any format recognized as human +The arc format reads two numeric fields, a latitude and a longitude, +in any format recognized as human readable and writes as simple degrees decimal. It really is intended for GPSBabel's own internal use more than general use, though -it turns out to be a convenient way of expressing simple polylines and +it turns out to be a convenient way of expressing simple polylines and polygons. diff --git a/xmldoc/formats/baroiq.xml b/xmldoc/formats/baroiq.xml index cd3d8fd11..46d7d42d0 100644 --- a/xmldoc/formats/baroiq.xml +++ b/xmldoc/formats/baroiq.xml @@ -1,5 +1,5 @@ Serial download protocol for the Brauniger IQ series of -barograph recording flight instruments. This format creates a -track of altitude vs time which can be merged with a GPS track +barograph recording flight instruments. This format creates a +track of altitude vs time which can be merged with a GPS track of the same flight to create a three dimensional IGC file. diff --git a/xmldoc/formats/bcr.xml b/xmldoc/formats/bcr.xml index 76915df69..1e750c56b 100644 --- a/xmldoc/formats/bcr.xml +++ b/xmldoc/formats/bcr.xml @@ -1,21 +1,21 @@ - -This file format (extension .bcr) is used in Map&Guide -Motorrad Routenplaner 2002 and later versions. -BCR is a route-only format. If you own a newer release (2005 or later) you -may also use the XML export with GPSBabel's tef -input format. + +This file format (extension .bcr) is used in Map&Guide +Motorrad Routenplaner 2002 and later versions. +BCR is a route-only format. If you own a newer release (2005 or later) you +may also use the XML export with GPSBabel's tef +input format. There may be other products from Map&Guide that use this format as well. - + Coordinates are stored in a BCR file in a Mercator projection. The -conversion from the Mercator projection to polar (latitude/longitude) -coordinates and back again may result in visible differences. Experience +conversion from the Mercator projection to polar (latitude/longitude) +coordinates and back again may result in visible differences. Experience reports are welcome. Sample BCR command with all options gpsbabel -r -i gpx -f in.gpx -o bcr,index=1,name="From A to B",radius=6371012 -F a_to_b.bcr - + diff --git a/xmldoc/formats/bushnell.xml b/xmldoc/formats/bushnell.xml index 47fbc7ee3..18ebfbc38 100644 --- a/xmldoc/formats/bushnell.xml +++ b/xmldoc/formats/bushnell.xml @@ -1,11 +1,11 @@ -This format supports reading and writing wayponts to -Bushnell GPS +This format supports reading and writing wayponts to +Bushnell GPS receivers, notably the Onix 400. -It's an oddity for many GPSBabel norms that this format requires each -waypoint be in a separate file. Our "output filename" argument, -F is +It's an oddity for many GPSBabel norms that this format requires each +waypoint be in a separate file. Our "output filename" argument, -F is modified to take an "output filename template". The output filename you specify will have a dash, and a sequentially increasing integer, and the ".wpt" extension appended to it. When the names are shown on @@ -30,7 +30,7 @@ Windows users may prefer the spelling: At least for the 200CR, the directory name used by the device is "WAYPOINT" in the root directory. It's also worth mentioning that its USB Mass Storage -protocol appears to not work on (at least) Snow Leopard 10.6.2. It's not +protocol appears to not work on (at least) Snow Leopard 10.6.2. It's not known if other Onix models have a more compatible USB implementation. diff --git a/xmldoc/formats/bushnell_trl.xml b/xmldoc/formats/bushnell_trl.xml index a4ed29afe..fbd7922f3 100644 --- a/xmldoc/formats/bushnell_trl.xml +++ b/xmldoc/formats/bushnell_trl.xml @@ -1,12 +1,12 @@ -This format supports tracks from -Bushnell GPS +This format supports tracks from +Bushnell GPS receivers, notably the Onix 400. This format reads individual .trl files as written by the GPS. As this is -a reverse-engineered format, it's not understood how (or even if) long -tracks, in +a reverse-engineered format, it's not understood how (or even if) long +tracks, in particular, span multiple files so initially this format is most effective on tracks under a few thousand points. @@ -15,7 +15,7 @@ on tracks under a few thousand points. most we believe these units can represent in a track. - The output base filename, converted to uppercase and stripped of - everything but letters and digits, is used for the trail name inside + The output base filename, converted to uppercase and stripped of + everything but letters and digits, is used for the trail name inside the file itself. diff --git a/xmldoc/formats/cambridge.xml b/xmldoc/formats/cambridge.xml index 5d8d79b9d..e1f20a899 100644 --- a/xmldoc/formats/cambridge.xml +++ b/xmldoc/formats/cambridge.xml @@ -1,8 +1,8 @@ - - - Support for -Cambridge -and Winpilot + + + Support for +Cambridge +and Winpilot flight analysis and planning software for glider pilots. - + diff --git a/xmldoc/formats/coastexp.xml b/xmldoc/formats/coastexp.xml index 3356a9fff..8023c5634 100644 --- a/xmldoc/formats/coastexp.xml +++ b/xmldoc/formats/coastexp.xml @@ -1,8 +1,8 @@ - - + + This is the format used by CoastalExplorer. The format is XML with items uniquely identified by Windows-style UUIDs. http://www.rosepointnav.com - + diff --git a/xmldoc/formats/csv.xml b/xmldoc/formats/csv.xml index cc15d9f46..660b96e13 100644 --- a/xmldoc/formats/csv.xml +++ b/xmldoc/formats/csv.xml @@ -1,17 +1,17 @@ - + There are a billion variants of Comma Separated Value data. This is the one specifically that makes DeLorme S&A Deluxe 9 happy. It's also a very simple program and useful for many other programs like spreadsheets, but contains only a very minimal information. For general -purpose use, you'll probably be more happy with our +purpose use, you'll probably be more happy with our universal csv (unicsv) format. - CSV is also the correct format for + CSV is also the correct format for Lowrance MapCreate, their commercial mapping program, or GDM6 (their free waypoint manager) for iFinder which is available at lowrance.com - On write, this format writes simple "latitude, longitude" pairs, but + On write, this format writes simple "latitude, longitude" pairs, but on read it will read anything supported by our human readable definition. diff --git a/xmldoc/formats/cup.xml b/xmldoc/formats/cup.xml index 487060288..d48199814 100644 --- a/xmldoc/formats/cup.xml +++ b/xmldoc/formats/cup.xml @@ -1,10 +1,10 @@ - This format supports flight analysis data from the - See You + This format supports flight analysis data from the + See You program. - Position information is preserved, but the aviation-specific + Position information is preserved, but the aviation-specific information such as runway length and airport frequency, are written as blanks and ignored on read. diff --git a/xmldoc/formats/custom.xml b/xmldoc/formats/custom.xml index fdb1ef7e9..595333d8f 100644 --- a/xmldoc/formats/custom.xml +++ b/xmldoc/formats/custom.xml @@ -3,7 +3,7 @@ This format is not actually used by any real product. It is most useful for debugging purposes when developing a new format module for GPSBabel. -To understand the contents of this file, look at the +To understand the contents of this file, look at the style/custom.style file in the GPSBabel source distribution as well as . diff --git a/xmldoc/formats/destinator_trl.xml b/xmldoc/formats/destinator_trl.xml index fb78e4b16..ffddbfd58 100644 --- a/xmldoc/formats/destinator_trl.xml +++ b/xmldoc/formats/destinator_trl.xml @@ -3,8 +3,8 @@ The basic information was found at mozoft.com. - In addition to the standard GPS track data of coordinates and timestamp, this format also stores the - position fix and the number of satellites seen during recording. + In addition to the standard GPS track data of coordinates and timestamp, this format also stores the + position fix and the number of satellites seen during recording. Destinator by diff --git a/xmldoc/formats/dg-100.xml b/xmldoc/formats/dg-100.xml index a8240653f..d34baa6f6 100644 --- a/xmldoc/formats/dg-100.xml +++ b/xmldoc/formats/dg-100.xml @@ -1,11 +1,11 @@ - Serial download protocol for the GlobalSat DG-100, - GlobalSat BT-335, + Serial download protocol for the GlobalSat DG-100, + GlobalSat BT-335, and GlboalSat BT-338XGPS data loggers. - While the DG-100 has a button to record waypoints, they seem to be indistinguishable - from trackpoints. Therefore, all points will be presented as trackpoints, + While the DG-100 has a button to record waypoints, they seem to be indistinguishable + from trackpoints. Therefore, all points will be presented as trackpoints, regardless of whether they were recorded automatically or manually. diff --git a/xmldoc/formats/dmtlog.xml b/xmldoc/formats/dmtlog.xml index 818bd62eb..0480ecbf0 100644 --- a/xmldoc/formats/dmtlog.xml +++ b/xmldoc/formats/dmtlog.xml @@ -1,11 +1,11 @@ This format can be used to convert files from - TrackLogs Digital Mapping. The files + TrackLogs Digital Mapping. The files have extension .trl and can contain waypoints and tracks. - We have seen three different types of this format. Two are binary - and one is an XML based format. All three types are supported + We have seen three different types of this format. Two are binary + and one is an XML based format. All three types are supported by our reader. diff --git a/xmldoc/formats/dna.xml b/xmldoc/formats/dna.xml index 567f91688..062f481ba 100644 --- a/xmldoc/formats/dna.xml +++ b/xmldoc/formats/dna.xml @@ -4,4 +4,4 @@ command. Reading the binary Markers.jwp format directly off the data card is not supported yet. Contributed by Tim Zickus. - + diff --git a/xmldoc/formats/easygps.xml b/xmldoc/formats/easygps.xml index 100150d47..699c41aae 100644 --- a/xmldoc/formats/easygps.xml +++ b/xmldoc/formats/easygps.xml @@ -8,4 +8,4 @@ Information about and sketchy code to implement this file format were provided by Eric Cloninger. - + diff --git a/xmldoc/formats/energympro.xml b/xmldoc/formats/energympro.xml index ca4d57fef..817e0e054 100644 --- a/xmldoc/formats/energympro.xml +++ b/xmldoc/formats/energympro.xml @@ -5,9 +5,9 @@ The Energympro GPS sport watches present themselves as USB mass storage - devices. To get the training just connect the device using the supplied -USB cable to your computer and the device will show up as a removable device. -Your training data is in the Workout folder. + devices. To get the training just connect the device using the supplied +USB cable to your computer and the device will show up as a removable device. +Your training data is in the Workout folder. diff --git a/xmldoc/formats/enigma.xml b/xmldoc/formats/enigma.xml index dcb1ef0ce..a336dd042 100644 --- a/xmldoc/formats/enigma.xml +++ b/xmldoc/formats/enigma.xml @@ -1,11 +1,11 @@ - - This MGL Avionics format holds waypoints or routes. This routes can be loaded by the MGL Stratomaster Enigma EFIS series ( -Enigma, -Odyssey, -Voyager, -Explorer). - - - The format is designed for microcontrollers. The use is free for any non-military - application. You can find a detailed description in the MGL Documentation. - + + This MGL Avionics format holds waypoints or routes. This routes can be loaded by the MGL Stratomaster Enigma EFIS series ( +Enigma, +Odyssey, +Voyager, +Explorer). + + + The format is designed for microcontrollers. The use is free for any non-military + application. You can find a detailed description in the MGL Documentation. + diff --git a/xmldoc/formats/enigma_wp.xml b/xmldoc/formats/enigma_wp.xml index e627bf9b1..09a06468f 100644 --- a/xmldoc/formats/enigma_wp.xml +++ b/xmldoc/formats/enigma_wp.xml @@ -1,10 +1,10 @@ - - The MGL Avionics format holds waypoints or routes. These routes can be loaded by the MGL Stratomaster Enigma EFIS series ( -Enigma, -Odyssey, -Voyager, -Explorer). - - - The format is designed for microcontrollers. The use is free for any non-military application. You can find a detailed description in the MGL Documentation. - + + The MGL Avionics format holds waypoints or routes. These routes can be loaded by the MGL Stratomaster Enigma EFIS series ( +Enigma, +Odyssey, +Voyager, +Explorer). + + + The format is designed for microcontrollers. The use is free for any non-military application. You can find a detailed description in the MGL Documentation. + diff --git a/xmldoc/formats/exif.xml b/xmldoc/formats/exif.xml index e868b4bc6..b5381f8bd 100644 --- a/xmldoc/formats/exif.xml +++ b/xmldoc/formats/exif.xml @@ -1,6 +1,6 @@ - This format reads and writes GPS information embedded in - EXIF, + This format reads and writes GPS information embedded in + EXIF, the Exchangeable Image Format, data. EXIF is a standardized method of encoding data in pictures such as JPEG, TIFF, and WAV and is frequently used by mobile phones with cameras and cameras with built-in GPS. diff --git a/xmldoc/formats/f90g.xml b/xmldoc/formats/f90g.xml index 07e13baf1..7a12125b9 100644 --- a/xmldoc/formats/f90g.xml +++ b/xmldoc/formats/f90g.xml @@ -1,4 +1,4 @@ - + This format is for the .map files produced by the F90G automobile Digital Video Recorder (DVR) when recording videos. The files are diff --git a/xmldoc/formats/fit.xml b/xmldoc/formats/fit.xml index 12c71a848..b605c24f3 100644 --- a/xmldoc/formats/fit.xml +++ b/xmldoc/formats/fit.xml @@ -1,5 +1,5 @@ -This format supports Garmin FIT activity files, defined as part -of the ANT standard. These are generated by newer Garmin +This format supports Garmin FIT activity files, defined as part +of the ANT standard. These are generated by newer Garmin devices like the ForeRunner 110. diff --git a/xmldoc/formats/fugawi.xml b/xmldoc/formats/fugawi.xml index ab1d09fad..7574023d8 100644 --- a/xmldoc/formats/fugawi.xml +++ b/xmldoc/formats/fugawi.xml @@ -1,6 +1,6 @@ - - + + This was a requested CSV format, and is not the proprietary binary format used by Fugawi. Like any other CSV format, GPSBabel cannot read tracks in this format, but converting a track into it and @@ -24,4 +24,4 @@ Fugawi): http://www.fugawi.com/ - + diff --git a/xmldoc/formats/gdb.xml b/xmldoc/formats/gdb.xml index b1a8afec1..a26113653 100644 --- a/xmldoc/formats/gdb.xml +++ b/xmldoc/formats/gdb.xml @@ -1,13 +1,13 @@ - + Support for the "Garmin GPS Database" format used by - default in MapSource versions since release 6.0 of + default in MapSource versions since release 6.0 of that product. By default GPSBabel creates gdb files of version 2. Version 2 is used in Mapsource 6.3 and 6.5. This format is also used by Garmin BaseCamp for Mac and Windows. - + Garmin GPS database is an undocumented file format. The basic info for this module came from the existing MapSource conversion code. - + diff --git a/xmldoc/formats/geo.xml b/xmldoc/formats/geo.xml index 54e589f33..127abb445 100644 --- a/xmldoc/formats/geo.xml +++ b/xmldoc/formats/geo.xml @@ -1,14 +1,14 @@ This format supports the Geocaching.com/EasyGPS ".loc" format. This format -was created specifically for Geocaching.com and is not the same as the -standard EasyGPS .loc format. See the EasyGPS +was created specifically for Geocaching.com and is not the same as the +standard EasyGPS .loc format. See the EasyGPS or GPX formats for more general EasyGPS support. -This is a simple XML-based format containing only very basic information -about geocaches. If you can use the GPX +This is a simple XML-based format containing only very basic information +about geocaches. If you can use the GPX format from Pocket Queries instead, you should consider doing so as it is a much richer format. -We have a separate page describing how to send from Geocaching.com pages to GPS +We have a separate page describing how to send from Geocaching.com pages to GPS diff --git a/xmldoc/formats/geojson.xml b/xmldoc/formats/geojson.xml index 4a9672864..1f7d238d8 100644 --- a/xmldoc/formats/geojson.xml +++ b/xmldoc/formats/geojson.xml @@ -2,15 +2,15 @@ This module supports a subset of the GeoJSON format. -GeoJSON is a poor fit for GPSBabel's internal data structures as GPSBabel -was designed more around common GPS features (waypoints, tracks, routes) +GeoJSON is a poor fit for GPSBabel's internal data structures as GPSBabel +was designed more around common GPS features (waypoints, tracks, routes) than about GIS-style concepts like MultiPolygons or Geometry Collections. In reality, for all but the most simple uses (such as converting a format that GPSBabel supports well to something like Leaflet, you should not expect high fidelity transfers through this format. -Waypoints are mapped to a FeatureCollection of Points. +Waypoints are mapped to a FeatureCollection of Points. The properties for name and description are written, where available. Tracks are converted to a LineString. MultiPoint are converted to Waypoints. @@ -18,7 +18,7 @@ LineString, Polygon and MultiPolygon are converted to routes. MultiLineString are converted to tracks. -The potentially nested/recursive nature of GeoJSON in general would be +The potentially nested/recursive nature of GeoJSON in general would be an awkward implementation. diff --git a/xmldoc/formats/ggv_log.xml b/xmldoc/formats/ggv_log.xml index 9b76cc725..d5fcdf584 100644 --- a/xmldoc/formats/ggv_log.xml +++ b/xmldoc/formats/ggv_log.xml @@ -3,10 +3,10 @@ popular product in Germany. - GPSBabel has full support for version 1.0 of this file format. + GPSBabel has full support for version 1.0 of this file format. - We can also read some GPS data (including coordinates) from version 2.5. But - it seems, that this newer version no longer stores time stamps. This can be + We can also read some GPS data (including coordinates) from version 2.5. But + it seems, that this newer version no longer stores time stamps. This can be a problem when converting to other formats or if you want to use our track filter. diff --git a/xmldoc/formats/ggv_ovl.xml b/xmldoc/formats/ggv_ovl.xml index 72772f590..6e2078a39 100644 --- a/xmldoc/formats/ggv_ovl.xml +++ b/xmldoc/formats/ggv_ovl.xml @@ -1,5 +1,5 @@ - Overlay files used by Geogrid-Viewer has to be in ASCII format. + Overlay files used by Geogrid-Viewer has to be in ASCII format. Make sure you save the files correctly. @@ -7,7 +7,7 @@ converted to tracks, except they are grouped. In this case GPSBabel creates routes. - During the creation of an overlay file, a circle will be added to each + During the creation of an overlay file, a circle will be added to each position of a waypoint or a route. diff --git a/xmldoc/formats/glogbook.xml b/xmldoc/formats/glogbook.xml index 877bd1b72..82a05b2f0 100644 --- a/xmldoc/formats/glogbook.xml +++ b/xmldoc/formats/glogbook.xml @@ -1,9 +1,9 @@ This is the XML format used by the Garmin Logbook product - that ships with Forerunner and Foretrex. + that ships with Forerunner and Foretrex. As of early 2006, this program is apparently been discontinued in favor of Garmin Training Center. - See: http://www.garmin.com + See: http://www.garmin.com - + diff --git a/xmldoc/formats/googledir.xml b/xmldoc/formats/googledir.xml index c96e16dea..5b7c170ae 100644 --- a/xmldoc/formats/googledir.xml +++ b/xmldoc/formats/googledir.xml @@ -1,6 +1,6 @@ - - + + This format is designed to read the XML emitted when you use the Google Directions API. @@ -10,12 +10,12 @@ If you use a Unix-compatible operating system, this shell script might be useful: /dev/null >google_map.xml gpsbabel -i googledir -f google_map.xml -o gpx -F google_map.gpx ]]> - + diff --git a/xmldoc/formats/gpl.xml b/xmldoc/formats/gpl.xml index dbe40abc3..2f16e472e 100644 --- a/xmldoc/formats/gpl.xml +++ b/xmldoc/formats/gpl.xml @@ -1,7 +1,7 @@ This is the 'gpl' format as used in DeLorme mapping products. It is a track format and contains little more than the - tracklog of a GPS that was attached while driving. + tracklog of a GPS that was attached while driving. frontiernet.net - + diff --git a/xmldoc/formats/gpsdrive.xml b/xmldoc/formats/gpsdrive.xml index d4522f8d8..2f6c7a806 100644 --- a/xmldoc/formats/gpsdrive.xml +++ b/xmldoc/formats/gpsdrive.xml @@ -1,7 +1,7 @@ - - + + GpsDrive way.txt file format. A space separated format file. Tested against GpsDrive v 1.30 found at gpsdrive.de. Contributed by Alan Curry. - + diff --git a/xmldoc/formats/gpsdrivetrack.xml b/xmldoc/formats/gpsdrivetrack.xml index 416ec0095..9e26a08bf 100644 --- a/xmldoc/formats/gpsdrivetrack.xml +++ b/xmldoc/formats/gpsdrivetrack.xml @@ -1,7 +1,7 @@ - - + + Format used by GpsDrive to save tracks. Like GPSDRIVE a space separated format file. See above for a link to GpsDrive. Contributed by Tobias Minich. - + diff --git a/xmldoc/formats/gpx.xml b/xmldoc/formats/gpx.xml index 1a26b38e8..e1fba6f6e 100644 --- a/xmldoc/formats/gpx.xml +++ b/xmldoc/formats/gpx.xml @@ -12,4 +12,4 @@ really understand. It also tries to glean interesting data from: Humminbird's "h" GPX extensions. - + diff --git a/xmldoc/formats/gtrnctr.xml b/xmldoc/formats/gtrnctr.xml index 6584bfd5e..82e0e34b6 100644 --- a/xmldoc/formats/gtrnctr.xml +++ b/xmldoc/formats/gtrnctr.xml @@ -1,11 +1,11 @@ -GPSBabel supports reading and writing of tracks in the .tcx -format used by Garmin Training Center (GTC). GTC is the successor -to Garmin's Logbook program for their workout units. It is a +GPSBabel supports reading and writing of tracks in the .tcx +format used by Garmin Training Center (GTC). GTC is the successor +to Garmin's Logbook program for their workout units. It is a free upgrade. -GPSBabel can read GTC v1 and v2 files, and can write v2 files. +GPSBabel can read GTC v1 and v2 files, and can write v2 files. v2 files are most likely to have a .tcx extension. v1 files typically have a .hst or .crs extension, depending on whether they are in the "history" or "course" format. @@ -15,20 +15,20 @@ There is a fundamental mismatch between this format and most of what we support. GPSBabel deals in waypoints, tracks, and routes. While we do record things like heart rate and temperature when we know it, the fundamentals of Training Center are different. It deals in -concepts like laps and calories, which are rather alien to GPSBabel +concepts like laps and calories, which are rather alien to GPSBabel and most of the formats we support. As such, while we can describe the tracks pretty accurately, things like calories and heart zone tracking are not supported. Some of the auxiliary data, such as heart rate (not zone), cadence, and bicycling power are supported. -One of the most useful things you can do with this format is to send -.tcx files found on the web or elsewhere to any supported GPS -unit. You will probably want to include the transform (rte=trk) +One of the most useful things you can do with this format is to send +.tcx files found on the web or elsewhere to any supported GPS +unit. You will probably want to include the transform (rte=trk) and simplify filters in this process. For example, -gpsbabel -i gtrnctr -f somefile.tcx -x simplify,count=50 +gpsbabel -i gtrnctr -f somefile.tcx -x simplify,count=50 -x transform,rte=trk -r -o garmin -F usb: diff --git a/xmldoc/formats/hiketech.xml b/xmldoc/formats/hiketech.xml index b9219caf7..21c10f821 100644 --- a/xmldoc/formats/hiketech.xml +++ b/xmldoc/formats/hiketech.xml @@ -1,7 +1,7 @@ This is the .gps format used by the Mac OS X applications written by HikeTech. These include TopoDraw, Link2GPS, and GPSWrite. - More information about these products can be found at + More information about these products can be found at hiketech.com - + diff --git a/xmldoc/formats/holux.xml b/xmldoc/formats/holux.xml index 3f52671cf..144712199 100644 --- a/xmldoc/formats/holux.xml +++ b/xmldoc/formats/holux.xml @@ -1,6 +1,6 @@ - - + + The Holux gm-100 (e-fox) gps receiver uses standard compact flash cards. File formats were provided by Holux-Taiwan holux.com to the author. @@ -25,4 +25,4 @@ version 1.14. This program is free of charge from the Holux web site. This format was contributed by Jochen Becker. - + diff --git a/xmldoc/formats/hsandv.xml b/xmldoc/formats/hsandv.xml index 88847d68c..8d82b85e2 100644 --- a/xmldoc/formats/hsandv.xml +++ b/xmldoc/formats/hsandv.xml @@ -1,8 +1,8 @@ - - + + HSA Systems Endeavour Navigator format - will import both the old version 4.x binary files, and the newer XML based ones. Only writes the new XML (5.0 and above) format. (use the .exp extension) - + diff --git a/xmldoc/formats/html.xml b/xmldoc/formats/html.xml index 1c53699a3..c99e025ec 100644 --- a/xmldoc/formats/html.xml +++ b/xmldoc/formats/html.xml @@ -1,8 +1,8 @@ - + GPSBabel's HTML output generates a single HTML file of all of the waypoints in the input file. It supports a number of Groundspeak GPX extensions and filters out potentially harmful HTML from the - input file while maintaining almost all of the source HTML formatting. + input file while maintaining almost all of the source HTML formatting. This makes this format well suited for generating HTML to hand to programs like Plucker for putting in a PDA and especially so for "paperless caching" for Geocachers with pocket queries. @@ -18,4 +18,4 @@ gpsbabel -i gpx -f 12345.gpx -o html,stylesheet=green.css,encrypt -F 12345.html - + diff --git a/xmldoc/formats/humminbird.xml b/xmldoc/formats/humminbird.xml index ec3739161..2a8b86d5a 100644 --- a/xmldoc/formats/humminbird.xml +++ b/xmldoc/formats/humminbird.xml @@ -13,7 +13,7 @@ - If you do "save all nav data" on the device, you'll get a + If you do "save all nav data" on the device, you'll get a data.hwr and a 000.ht file on the flash card (on a 797 in the matrix directory). @@ -22,11 +22,11 @@ tell it which ones to write. By default, you get a .hwr file, to get a track (.ht file), use the "humminbird-track" format. - + - + Note:.dat files are read-only, they only make sense @@ -38,7 +38,7 @@ together with their images. 797c2i SI (They should all work, but this is the only one tested so far.) - + Known limits: diff --git a/xmldoc/formats/iblue757.xml b/xmldoc/formats/iblue757.xml index f29e4e148..bc3e5f34e 100644 --- a/xmldoc/formats/iblue757.xml +++ b/xmldoc/formats/iblue757.xml @@ -1,14 +1,14 @@ - This is the format used by the software that comes with the + This is the format used by the software that comes with the Transystem i-Blue757 Pro GPS . - It is very similar to the iBlue747 + It is very similar to the iBlue747 format, apart from the date format being reversed. - The csv log file can be extracted from the GPS receiver using + The csv log file can be extracted from the GPS receiver using the BT747 software available from diff --git a/xmldoc/formats/ignrando.xml b/xmldoc/formats/ignrando.xml index aedde6626..93d6e9998 100644 --- a/xmldoc/formats/ignrando.xml +++ b/xmldoc/formats/ignrando.xml @@ -1,6 +1,6 @@ -This format supports IGN Rando track files. IGN Rando is a program mainly -used in France for Topo maps. The files are XML based and are "windows-1252" +This format supports IGN Rando track files. IGN Rando is a program mainly +used in France for Topo maps. The files are XML based and are "windows-1252" encoded. Trackpoints do not have time stamps. - + diff --git a/xmldoc/formats/igo2008_poi.xml b/xmldoc/formats/igo2008_poi.xml index e663785ab..c5b1fa4c0 100644 --- a/xmldoc/formats/igo2008_poi.xml +++ b/xmldoc/formats/igo2008_poi.xml @@ -1,5 +1,5 @@ igo2008_poi supports POI files from Nav N Go iGO 8 Europe. - This is a GPS Navigation Software for Windows Mobile based + This is a GPS Navigation Software for Windows Mobile based PDA devices and Smartphones. diff --git a/xmldoc/formats/ik3d.xml b/xmldoc/formats/ik3d.xml index bfabade27..b08673222 100644 --- a/xmldoc/formats/ik3d.xml +++ b/xmldoc/formats/ik3d.xml @@ -6,6 +6,6 @@ route-planning software with a 3-dimensional environment. - The project files are XML based and we can read the main GPS items (names and coordinates). + The project files are XML based and we can read the main GPS items (names and coordinates). For an output these files are too complex. diff --git a/xmldoc/formats/kml.xml b/xmldoc/formats/kml.xml index 98fb8ab65..585e1f4ba 100644 --- a/xmldoc/formats/kml.xml +++ b/xmldoc/formats/kml.xml @@ -1,10 +1,10 @@ - -KML, the Keyhole Markup Language format, was used by Keyhole and is used by -Google Earth. + +KML, the Keyhole Markup Language format, was used by Keyhole and is used by +Google Earth. -There are concepts in KML that GPSBabel can't support very well on +There are concepts in KML that GPSBabel can't support very well on read because they don't map well into other programs. For example, KML has -ideas of camera views and names and descriptions can have arbitrarily +ideas of camera views and names and descriptions can have arbitrarily complicated HTML in them. KML files may have tiered "Styles" which can identify sizing info and URLs of associated icons. Reading such files with GPSBabel - even if your goal it to write it back out as KML - can often @@ -19,9 +19,9 @@ and several file format imports and exports. In general, GPSBabel's KML writer is relatively strong. GPSBabel handles simple KML on read fairly well, but if you're dealing with handcrafted KML that uses extensive features that have no analog in other formats like nested folders, ringgeometry, camera angles, and such, don't expect GPSBabel to do well with them on read. - Google Earth 4.0 and later have a feature that can surprise users of this + Google Earth 4.0 and later have a feature that can surprise users of this format. Earth's "time slider" feature controls what timestamped data - gets displayed. If you're using data that has timestamps (e.g. GPX + gets displayed. If you're using data that has timestamps (e.g. GPX points that contain time or almost any track data) this will be important to you. The time slider defaults to the far left position and fully closed. This means that only the first data point will be displayed. You can diff --git a/xmldoc/formats/kompass_tk.xml b/xmldoc/formats/kompass_tk.xml index 6b49141a7..098b393fe 100644 --- a/xmldoc/formats/kompass_tk.xml +++ b/xmldoc/formats/kompass_tk.xml @@ -3,6 +3,6 @@ Kompass is a publishing company from Austria. - If you want to get more information about DAV, the German alpine association, + If you want to get more information about DAV, the German alpine association, and if you are familiar with the german language, please have a look at their homepage. diff --git a/xmldoc/formats/ktf2.xml b/xmldoc/formats/ktf2.xml index 31fd17dbf..5a56d36f4 100644 --- a/xmldoc/formats/ktf2.xml +++ b/xmldoc/formats/ktf2.xml @@ -1,3 +1,3 @@ Support for Kartex 5 trackfiles. For more info see kwf2. - + diff --git a/xmldoc/formats/kwf2.xml b/xmldoc/formats/kwf2.xml index 307caa1ff..61a636457 100644 --- a/xmldoc/formats/kwf2.xml +++ b/xmldoc/formats/kwf2.xml @@ -1,9 +1,9 @@ - - - Support for Kartex 5 waypoint files. Kartex is a Swedish - map and GPS positioning system. GPSBabel can read and write - files from Kartex 4 and 5 with WGS84 coordinates. UTM or + + + Support for Kartex 5 waypoint files. Kartex is a Swedish + map and GPS positioning system. GPSBabel can read and write + files from Kartex 4 and 5 with WGS84 coordinates. UTM or Swedish grid are not supported. - + diff --git a/xmldoc/formats/lmx.xml b/xmldoc/formats/lmx.xml index f668be441..3e0e4b65d 100644 --- a/xmldoc/formats/lmx.xml +++ b/xmldoc/formats/lmx.xml @@ -1,4 +1,4 @@ - + This format supports Nokia Landmark Exchange (LMX) files used by several Nokia phones. diff --git a/xmldoc/formats/m241-bin.xml b/xmldoc/formats/m241-bin.xml index 1a448d56b..108f86d69 100644 --- a/xmldoc/formats/m241-bin.xml +++ b/xmldoc/formats/m241-bin.xml @@ -1,15 +1,15 @@ - The Holux m241 is a small datalogger using the MTK chipset, with - a couple small differences in the binary format. In its default + The Holux m241 is a small datalogger using the MTK chipset, with + a couple small differences in the binary format. In its default configuration, it can store ~100000 trackpoints with very limited - data; to configure extended logging you can use the BT747 open - source software + data; to configure extended logging you can use the BT747 open + source software bt747 Waypoint storage is possible only if "recording reason" (RCR) is enabled in the settings. - Holux GPSport 245 is a datalogger with display suitable for cycling, walking and running. - It can store ~200k trackpoints with limited data. The m241 and m241-bin format is + Holux GPSport 245 is a datalogger with display suitable for cycling, walking and running. + It can store ~200k trackpoints with limited data. The m241 and m241-bin format is able to automatically detect GPSport 245 data and handle the differences from Holux M-241 devices. Note: GP245 does not log any quality of the position. diff --git a/xmldoc/formats/magellan.xml b/xmldoc/formats/magellan.xml index 7cb28f149..1c5a47005 100644 --- a/xmldoc/formats/magellan.xml +++ b/xmldoc/formats/magellan.xml @@ -22,14 +22,14 @@ Explorist XL - + This format is used for both the serial protocol used on the devices with serial ports such as Map330 and Meridian and for - the files stored either in either the unit's internal memory - (Explorist 210, Explorist 400, Explorist 500, Explorist 600, + the files stored either in either the unit's internal memory + (Explorist 210, Explorist 400, Explorist 500, Explorist 600, Explorist XL) or on removable memory. - + If you specify a serial port for the file (.e.g. "COM1", "/dev/ttyS0") to be read or written, GPSBabel will use serial protocol. Specifying diff --git a/xmldoc/formats/magellan1.xml b/xmldoc/formats/magellan1.xml index 831285c8b..331bec64d 100644 --- a/xmldoc/formats/magellan1.xml +++ b/xmldoc/formats/magellan1.xml @@ -25,13 +25,13 @@ The RoadMate family of products is not supported. - + This format is used for both the serial protocol used on the devices with serial ports such as Map330 and Meridian and for - the files stored either in either the unit's internal memory + the files stored either in either the unit's internal memory (Explorist 210, 400, 500, 600, XL) or on removable memory. - + If you specify a serial port for the file (.e.g. "COM1", "/dev/ttyS0") to be read or written, GPSBabel will use serial protocol. Specifying diff --git a/xmldoc/formats/magellanx.xml b/xmldoc/formats/magellanx.xml index ffb219fb5..179a7f3c5 100644 --- a/xmldoc/formats/magellanx.xml +++ b/xmldoc/formats/magellanx.xml @@ -1,14 +1,14 @@ This is the SD card format used by the Magellan Explorist 400, - Explorist 500, Explorist 600, and Explorist XL and internally on those devices plus the + Explorist 500, Explorist 600, and Explorist XL and internally on those devices plus the Explorist 210. Stored waypoints are identical to the Magellan SD format - used by Meridian, but the newer models allow longer waypoint names. Routes are + used by Meridian, but the newer models allow longer waypoint names. Routes are subtly different. - - You should name any file containing waypoints created with + + You should name any file containing waypoints created with this format with a ".upt" extension so the firmware can read it. Similarly, routes should be named ".rte" and tracks should be named ".log". - + diff --git a/xmldoc/formats/mapasia_tr7.xml b/xmldoc/formats/mapasia_tr7.xml index f478d4451..5ef2c2bbc 100644 --- a/xmldoc/formats/mapasia_tr7.xml +++ b/xmldoc/formats/mapasia_tr7.xml @@ -1,6 +1,6 @@ - Mapking provides a set of tools for GPS - navigation.  The location of distributed maps is mainly in Asia, so the software seems - not (yet) well known in Europe or US.  Some of the GPS tools (e.g. Mapking 2007 for Windows Mobile) + Mapking provides a set of tools for GPS + navigation.  The location of distributed maps is mainly in Asia, so the software seems + not (yet) well known in Europe or US.  Some of the GPS tools (e.g. Mapking 2007 for Windows Mobile) can also be used to write waypoints and save them under the .tr7 format which can be translated by GPSBabel. diff --git a/xmldoc/formats/mapbar.xml b/xmldoc/formats/mapbar.xml index a27bc81f3..898ee5bcb 100644 --- a/xmldoc/formats/mapbar.xml +++ b/xmldoc/formats/mapbar.xml @@ -2,7 +2,7 @@ This format is the Mapbar navigation programs used on phones such as the Sonim XP3300 popular in China. The files are found on the sd card in /mapbar/userdata/tracks. - This format just logs track point by latitude and longitude; no time + This format just logs track point by latitude and longitude; no time information is available. @@ -11,7 +11,7 @@ software version: 3.73.47.39836, data version: B29. The following devices of using mapbar navigation are supported. Other -devices with using mapbar navigation maybe be supported, but not have +devices with using mapbar navigation maybe be supported, but not have not been tested: Sonim Xp3300(China version) diff --git a/xmldoc/formats/mapconverter.xml b/xmldoc/formats/mapconverter.xml index 3c9fa9dab..7a2634109 100644 --- a/xmldoc/formats/mapconverter.xml +++ b/xmldoc/formats/mapconverter.xml @@ -3,7 +3,7 @@ Mapconverter is a format that is read by Mapopolis.com's mapconverter application. -Mapconverter is an application used to create userland maps and map data for +Mapconverter is an application used to create userland maps and map data for Mapopolis.com's Mapopolis program. The mapconverter format is essentially waypoint data prepared in a format that the mapconverter application will accept. @@ -30,7 +30,7 @@ on your PDA. GPSBabel will write the name of its own output file in the output file - it creates as the input for Mapconverter. Mapconverter will replace + it creates as the input for Mapconverter. Mapconverter will replace the extension of this filename with ".pdb". @@ -52,7 +52,7 @@ Mapconverter only works with Mapopolis version 3.x. Mapopolis version Mapconverter is no longer available from the Mapopolis website. If you need a copy of mapconverter, ask on your local GPS Software discussion - forum and I'm sure someone will have it. As far as I know, It was never + forum and I'm sure someone will have it. As far as I know, It was never actually acknowledged/supported by Mapopolis to begin with. diff --git a/xmldoc/formats/miniHomer.xml b/xmldoc/formats/miniHomer.xml index e3657309f..38d25e0fc 100644 --- a/xmldoc/formats/miniHomer.xml +++ b/xmldoc/formats/miniHomer.xml @@ -1,7 +1,7 @@ -Serial download protocol for GPS data loggers called "miniHomer". +Serial download protocol for GPS data loggers called "miniHomer". These loggers are based on Skytraq Venus 5 and Venus 6 chipsets, but with modified firmware. -The miniHomer logger has five POI (or better: Point-to-Return, PTR?), which can be set programatically. The miniHomer module in gpsbabel is an extension of the skytraq module. +The miniHomer logger has five POI (or better: Point-to-Return, PTR?), which can be set programatically. The miniHomer module in gpsbabel is an extension of the skytraq module. @@ -14,9 +14,9 @@ Following a list of devices which should be supported by this module - Manufacturer - Model - USB (baud) + Manufacturer + Model + USB (baud) Bluetooth (baud) @@ -44,8 +44,8 @@ Following a list of devices which should be supported by this module gpsbabel -i miniHomer,erase,no-output -f /dev/ttyUSB0 -miniHomer has five POI called Home, Car, Boat, Heart, Bar. You can set the lla -(Latitude, Longitude, Altitude) for each of the POI. The format is +miniHomer has five POI called Home, Car, Boat, Heart, Bar. You can set the lla +(Latitude, Longitude, Altitude) for each of the POI. The format is <name>=<lat>:<lng>[:<alt>] Once the according POI symbol is selected on miniHomer, the display shows you the direction and distance to the POI. @@ -56,7 +56,7 @@ Once the according POI symbol is selected on miniHomer, the display shows you th gpsbabel -i miniHomer,Car=36.790145:-6.352898,Home=-3.066667:37.359167:5895 -f /dev/ttyUSB0 -o gpx -F out.gpx Sets the Car/Home symbols' latitude longitude and altitude. - If you select the Car/Home symbol on miniHomer, the display will show the direction and distance to + If you select the Car/Home symbol on miniHomer, the display will show the direction and distance to this location as soon as it has a satellite fix. diff --git a/xmldoc/formats/mmo.xml b/xmldoc/formats/mmo.xml index 4f06d3931..27eae1d03 100644 --- a/xmldoc/formats/mmo.xml +++ b/xmldoc/formats/mmo.xml @@ -13,6 +13,6 @@ which causes errors, please provide it [mailto:gpsbabel-misc@lists.sourceforge.net]. - More information can be found at the + More information can be found at the Memory-Map site. diff --git a/xmldoc/formats/motoactv.xml b/xmldoc/formats/motoactv.xml index 871e3b495..d802e5533 100644 --- a/xmldoc/formats/motoactv.xml +++ b/xmldoc/formats/motoactv.xml @@ -1,7 +1,7 @@ The MotoACTV smart watch creates csv format files. GPSBabel can read and write these files through -the xcsv format when using the included motoactv.style specification. +the xcsv format when using the included motoactv.style specification. The specific format of the csv file has changed over time, to diff --git a/xmldoc/formats/mtk-bin.xml b/xmldoc/formats/mtk-bin.xml index 6d5b0578b..9a186eba7 100644 --- a/xmldoc/formats/mtk-bin.xml +++ b/xmldoc/formats/mtk-bin.xml @@ -6,9 +6,9 @@ When using the csv option a MTK application compatible output file will also be It has been tested with Transystem i-Blue 747 but other devices should work as well (Qstarz BT-Q1000, iTrek Z1, ...) -All position items (including button push) will be listed as trackpoints in the output. -Log items due to button push are presented as waypoints. -In theory we would not add waypoints to the list of trackpoints. But as the MTK logger restart the +All position items (including button push) will be listed as trackpoints in the output. +Log items due to button push are presented as waypoints. +In theory we would not add waypoints to the list of trackpoints. But as the MTK logger restart the log session from the button press we would loose a trackpoint unless we include/duplicate it. diff --git a/xmldoc/formats/mtk.xml b/xmldoc/formats/mtk.xml index ef9004062..3543f3b58 100644 --- a/xmldoc/formats/mtk.xml +++ b/xmldoc/formats/mtk.xml @@ -1,60 +1,60 @@ - This format is the serial download protocol for the MTK chips. - Mediatek's MT3301/3179 (MTKv1) and MT3318 (MTKv2) chips are used - in a large number of products sold under different names. + This format is the serial download protocol for the MTK chips. + Mediatek's MT3301/3179 (MTKv1) and MT3318 (MTKv2) chips are used + in a large number of products sold under different names. - Many GPS products, especially of the data logger variety, expose - the Mediatek protocol to the user via USB. Some modify Mediatek's - protocol in minor ways, but the core protocol is very commonly - seen in loggers. + Many GPS products, especially of the data logger variety, expose + the Mediatek protocol to the user via USB. Some modify Mediatek's + protocol in minor ways, but the core protocol is very commonly + seen in loggers. - The Holux M-241 and GPSport 245 - are examples of a device using an incompatible variation of the MTK + The Holux M-241 and GPSport 245 + are examples of a device using an incompatible variation of the MTK protocol. The following products are known or are expected to work with this module. -As the products are typically very low cost, they tend to have a short -product life cycle and are often imported to different areas under +As the products are typically very low cost, they tend to have a short +product life cycle and are often imported to different areas under different names. Keeping track of the list is difficult. Often the "same" GPS is sold in different -plastic or with different Windows software or different options such as +plastic or with different Windows software or different options such as compass or motion sensors or charging cables with different model numbers. If you can confirm success with others, please share with us. - + Devices supported by MTK module - Product - Confirmed to work - Notes + Product + Confirmed to work + Notes - iBlue 821 - Yes - Available from Semsons + iBlue 821 + Yes + Available from Semsons - iBlue 747, 747A+ - Yes - Available from Semsons + iBlue 747, 747A+ + Yes + Available from Semsons - QStarz BT-1000, BT-Q1000X, BT-1000eX - Yes - + QStarz BT-1000, BT-Q1000X, BT-1000eX + Yes + - iTrek Z1 - - + iTrek Z1 + + @@ -63,15 +63,15 @@ If you can confirm success with others, please share with us. The Mediatek chip offers a native serial port. Data logger designers frequently pair this with commodity USB/Serial converter internally. So - these devices typically look like Prolific, FTDI, or Silab usb/serial - devices to the host OS. You'll need drivers for that whatever chip + these devices typically look like Prolific, FTDI, or Silab usb/serial + devices to the host OS. You'll need drivers for that whatever chip your product uses for your operating system. For the "A+ GPS Recorder", the Silicon Labs CP210x chip is used. On OS/X, you'll get awesome device names like /dev/cu.usbmodem1d13410 - fortunately, our GUI makes that multiple choice so you don't have to guess. - Downloaded data will be stored in data.bin file in the current + Downloaded data will be stored in data.bin file in the current directory together with the chosen output format. This is a rather uncommon feature in GPSBabel's formats and is likely to change in future versions. @@ -83,16 +83,16 @@ If you can confirm success with others, please share with us. Command showing MTK download track and waypoints and erase on Linux gpsbabel -t -w -i mtk,erase -f /dev/ttyUSB0 -o gpx -F out.gpx - + - For more info and tweaks on MTK based loggers: + For more info and tweaks on MTK based loggers: MTK Tips and Tweaks and iBlue 747 Logger For info about the used log format, see MTK binary format -Most of the loggers cannot receive bluetooth commands; they can only send +Most of the loggers cannot receive bluetooth commands; they can only send data. Since GPSBabel needs to send commands to the GPS device it won't work. Download the data using the USB cable instead. diff --git a/xmldoc/formats/mtk_locus.xml b/xmldoc/formats/mtk_locus.xml index 48ff78d8e..38955d55f 100644 --- a/xmldoc/formats/mtk_locus.xml +++ b/xmldoc/formats/mtk_locus.xml @@ -1,8 +1,8 @@ -This format is a protocol supports the MediaTek MT3339, a GPS -chipset that shipped around 2011 that has internal logging capability. -It is the -core of at least two GPS modules, including the +This format is a protocol supports the MediaTek MT3339, a GPS +chipset that shipped around 2011 that has internal logging capability. +It is the +core of at least two GPS modules, including the GlobalTop PA6H and the Fastrax IT530. The GlobalTop PA6H module is in turn the heart of the Adafruit "Ultimate" GPS breakout board, popular in the Arduino "maker" world. diff --git a/xmldoc/formats/mxf.xml b/xmldoc/formats/mxf.xml index c5b511c46..a2f00ff14 100644 --- a/xmldoc/formats/mxf.xml +++ b/xmldoc/formats/mxf.xml @@ -1,8 +1,8 @@ - - + + Maptech Exchange Format - Another CSV format file. This format complies with (at least) Maptech Terrain Navigator, Terrain Professional, Take a Hike, and ExpertGPS import/export MFX. Contributed by Alex Mottram. - + diff --git a/xmldoc/formats/navigonwpt.xml b/xmldoc/formats/navigonwpt.xml index cae4274ef..66cb80df8 100644 --- a/xmldoc/formats/navigonwpt.xml +++ b/xmldoc/formats/navigonwpt.xml @@ -3,12 +3,12 @@ To actually manipulate the file on the unit, use a USB cable or SD card - reader and work with MN6\Settings\Favorites.storage + reader and work with MN6\Settings\Favorites.storage The waypoints are be created with a minimal amount of data; the unit will fill in the other fields on use. The other fields appear to be data the unit infers, such as nearby streets. - Note that this is the waypoint/placemark format (.storage) and not the + Note that this is the waypoint/placemark format (.storage) and not the route file format (.rte, .mn4) that is used by routes. diff --git a/xmldoc/formats/navilink.xml b/xmldoc/formats/navilink.xml index 7c5ed0c4c..19cf549ed 100644 --- a/xmldoc/formats/navilink.xml +++ b/xmldoc/formats/navilink.xml @@ -1,6 +1,6 @@ GPSBabel supports the Navilink protocol used by the - Locosys GT-11 + Locosys GT-11 and GT-31 GPS receivers. These are sold under a variety of names including: @@ -28,8 +28,8 @@ To access the device using the serial protocol over USB the device needs to be in Navilink mode, which can be activated - from the main menu of the device. This device uses a Prolific - PL2303 USB/Serial adapter internally and that's how it will + from the main menu of the device. This device uses a Prolific + PL2303 USB/Serial adapter internally and that's how it will present itself to the host operating system. You thus need USB drivers for the PL2303, such as those from the 'Download' section of diff --git a/xmldoc/formats/netstumbler.xml b/xmldoc/formats/netstumbler.xml index 4bdbfc777..07a1a6143 100644 --- a/xmldoc/formats/netstumbler.xml +++ b/xmldoc/formats/netstumbler.xml @@ -2,20 +2,20 @@ This format reads summary files from NetStumbler 0.4 or MacStumbler. - + The default behavior when creating waypoints is to use the SSID for the short name, and information about the access point for the description. When the SSID is not unique, is not available, or -consists of whitespace, a short name is synthesized. +consists of whitespace, a short name is synthesized. - + Different icons are assigned to encrypted, non-encrypted, stealth, and non-stealth access points; these may be -changed with options. +changed with options. NetStumbler -MacStumbler +MacStumbler diff --git a/xmldoc/formats/nima.xml b/xmldoc/formats/nima.xml index ea2790de4..3b49ae585 100644 --- a/xmldoc/formats/nima.xml +++ b/xmldoc/formats/nima.xml @@ -1,6 +1,6 @@ - - + + This is a CSV format from the National Imagery and Mapping Agency. - + diff --git a/xmldoc/formats/nmea.xml b/xmldoc/formats/nmea.xml index c78169c30..eb4fb6ecb 100644 --- a/xmldoc/formats/nmea.xml +++ b/xmldoc/formats/nmea.xml @@ -1,6 +1,6 @@ - - - This format is the file representation of the NMEA + + + This format is the file representation of the NMEA (National Marine Electronics Association) 0183 log and waypoint format for GPS devices. Some hardware and software that work with NMEA-0183 formatted data include: @@ -42,14 +42,14 @@ that work with NMEA-0183 formatted data include: Sony GPS_CS1 - + -This module also supports realtime tracking -which allows realtime position reports from a GPS, such as one connected +This module also supports realtime tracking +which allows realtime position reports from a GPS, such as one connected serially, over Bluetooth, or a USB module emulating a serial port, to be used with selected output formats. Just specify an input file that is the device name such as COM1: for Windows or a device-dependent name like -/dev/cu.usbserial for Mac or /dev/ttyUSB0 for Linux. (Note that serial +/dev/cu.usbserial for Mac or /dev/ttyUSB0 for Linux. (Note that serial device names vary on Mac and Linux.) diff --git a/xmldoc/formats/openoffice.xml b/xmldoc/formats/openoffice.xml index 8d6793b33..58424f011 100644 --- a/xmldoc/formats/openoffice.xml +++ b/xmldoc/formats/openoffice.xml @@ -1,4 +1,4 @@ - + Tab separated export-all (except geocaching data) file format. Intended to serve as source for number-processing applications like OpenOffice, Ploticus and others. Tab was chosen as diff --git a/xmldoc/formats/options/bcr-index.xml b/xmldoc/formats/options/bcr-index.xml index 2e960277d..7048b3187 100644 --- a/xmldoc/formats/options/bcr-index.xml +++ b/xmldoc/formats/options/bcr-index.xml @@ -1,7 +1,7 @@ -Because the format supports only one route, this option may be used -on output to select a single route from a collection of -routes read from a more expressive format. If you have, say, a +Because the format supports only one route, this option may be used +on output to select a single route from a collection of +routes read from a more expressive format. If you have, say, a gpx file that contains two routes, you may use this option to write them one at a time to individual files. diff --git a/xmldoc/formats/options/bcr-name.xml b/xmldoc/formats/options/bcr-name.xml index 575866e3a..b6ffe5238 100644 --- a/xmldoc/formats/options/bcr-name.xml +++ b/xmldoc/formats/options/bcr-name.xml @@ -1,5 +1,5 @@ This route specifies the name of the route. This is particularly useful if -the route came from an input format that did not support named routes, but +the route came from an input format that did not support named routes, but it may also be used to rename a route. diff --git a/xmldoc/formats/options/bcr-radius.xml b/xmldoc/formats/options/bcr-radius.xml index f41a98fa5..e4d059b39 100644 --- a/xmldoc/formats/options/bcr-radius.xml +++ b/xmldoc/formats/options/bcr-radius.xml @@ -1,6 +1,6 @@ -This option instructs GPSBabel to use a different value for the radius of -the earth when converting between the Mercator projection and geographic +This option instructs GPSBabel to use a different value for the radius of +the earth when converting between the Mercator projection and geographic coordinates. The default value is 6371000.0 meters. diff --git a/xmldoc/formats/options/cetus-appendicon.xml b/xmldoc/formats/options/cetus-appendicon.xml index 9a52e4eef..2baa34291 100644 --- a/xmldoc/formats/options/cetus-appendicon.xml +++ b/xmldoc/formats/options/cetus-appendicon.xml @@ -1,7 +1,7 @@ This option will add the icon description to the end of the waypoint description on output. This can be useful if the icon is used to convey -important information about the waypoint. For example, the icon might be +important information about the waypoint. For example, the icon might be "found geocache" or "unfound geocache"; it might be useful to know that when looking at a list of icons in Cetus. diff --git a/xmldoc/formats/options/delbin-gcsym.xml b/xmldoc/formats/options/delbin-gcsym.xml index 0475b4986..2c46e425c 100644 --- a/xmldoc/formats/options/delbin-gcsym.xml +++ b/xmldoc/formats/options/delbin-gcsym.xml @@ -1,8 +1,8 @@ -This 1/0 option, defaulting to if not provided, tells GPSBabel to -use its own logic when sending data it can deduce is a geocache to +This 1/0 option, defaulting to if not provided, tells GPSBabel to +use its own logic when sending data it can deduce is a geocache to the device. If false, any icon data present in the source data will be used instead. If you've taken control of the icon data, you are - responsible for providing valid icons; GPSBabel will make no attempt + responsible for providing valid icons; GPSBabel will make no attempt to purify what gets sent. diff --git a/xmldoc/formats/options/delbin-hint_at_and.xml b/xmldoc/formats/options/delbin-hint_at_and.xml index e4caeab25..f5cd8316d 100644 --- a/xmldoc/formats/options/delbin-hint_at_and.xml +++ b/xmldoc/formats/options/delbin-hint_at_and.xml @@ -1,5 +1,5 @@ - When set to true, this places the "HINT:" entry from a geocaching.com + When set to true, this places the "HINT:" entry from a geocaching.com pocket query at the end of the screen (scroll up for quick access) like Cache Register and Topo7 do instead of at the top as Topo8 does. diff --git a/xmldoc/formats/options/delbin-hint_at_end.xml b/xmldoc/formats/options/delbin-hint_at_end.xml index e4caeab25..f5cd8316d 100644 --- a/xmldoc/formats/options/delbin-hint_at_end.xml +++ b/xmldoc/formats/options/delbin-hint_at_end.xml @@ -1,5 +1,5 @@ - When set to true, this places the "HINT:" entry from a geocaching.com + When set to true, this places the "HINT:" entry from a geocaching.com pocket query at the end of the screen (scroll up for quick access) like Cache Register and Topo7 do instead of at the top as Topo8 does. diff --git a/xmldoc/formats/options/delbin-logs.xml b/xmldoc/formats/options/delbin-logs.xml index 18dbba8f4..11f9a6750 100644 --- a/xmldoc/formats/options/delbin-logs.xml +++ b/xmldoc/formats/options/delbin-logs.xml @@ -1,5 +1,5 @@ - When set to true, this includes Groundspeak logs from GPX pocket queries + When set to true, this includes Groundspeak logs from GPX pocket queries when writing to DeLorme devices that support the extended features introduced in firmware version 2.5 for the PN-40 and PN-30 and in 1.6 for the PN-20. diff --git a/xmldoc/formats/options/delbin-long_notes.xml b/xmldoc/formats/options/delbin-long_notes.xml index 86852fe75..f38e7ede7 100644 --- a/xmldoc/formats/options/delbin-long_notes.xml +++ b/xmldoc/formats/options/delbin-long_notes.xml @@ -1,10 +1,10 @@ - Use long waypoint notes, overriding the built-in version check (which is + Use long waypoint notes, overriding the built-in version check (which is reverse engineered) that tests if the unit can handle the waypoint comments longer than 800 bytes. This option will probably go away in time as most units get upgraded to - the capabilities of the 2.5 version of the PN-40 and PN-30 or version 1.6 + the capabilities of the 2.5 version of the PN-40 and PN-30 or version 1.6 for the PN-20. diff --git a/xmldoc/formats/options/delbin-nukewpt.xml b/xmldoc/formats/options/delbin-nukewpt.xml index 7b05be86f..397521b57 100644 --- a/xmldoc/formats/options/delbin-nukewpt.xml +++ b/xmldoc/formats/options/delbin-nukewpt.xml @@ -1,5 +1,5 @@ - When present on the command line and sending waypoints (either explicitly + When present on the command line and sending waypoints (either explicitly via -w or as the default), this will erase all waypoints in the receiver before sending the new ones. diff --git a/xmldoc/formats/options/dmtlog-index.xml b/xmldoc/formats/options/dmtlog-index.xml index 69cfb72c7..d0bb1fa89 100644 --- a/xmldoc/formats/options/dmtlog-index.xml +++ b/xmldoc/formats/options/dmtlog-index.xml @@ -3,9 +3,9 @@ The known variants of Tracklog 'digital mapping' files supports only - one track per file. If you have more than one track in source - (f.e MapSource and many others can do such heavy things), you - can specify which track should by used for the conversion. + one track per file. If you have more than one track in source + (f.e MapSource and many others can do such heavy things), you + can specify which track should by used for the conversion. The default index is 1 (the first track of a possible list of tracks). diff --git a/xmldoc/formats/options/exif-frame.xml b/xmldoc/formats/options/exif-frame.xml index c0014ceda..ac71f3259 100644 --- a/xmldoc/formats/options/exif-frame.xml +++ b/xmldoc/formats/options/exif-frame.xml @@ -1,6 +1,6 @@ Frame means the maximum time difference that we accept between the EXIF time information - of a picture and the timestamp of a track-, route- and waypoint used for tagging. + of a picture and the timestamp of a track-, route- and waypoint used for tagging. Without this option the maximum time frame is 10 seconds. diff --git a/xmldoc/formats/options/garmin-baud.xml b/xmldoc/formats/options/garmin-baud.xml index 04eb09b24..2743e1264 100644 --- a/xmldoc/formats/options/garmin-baud.xml +++ b/xmldoc/formats/options/garmin-baud.xml @@ -10,8 +10,8 @@ gpsbabel -t -w -i garmin,baud=115200 -f /dev/ttyUSB0 -o gpx -F garmin-serial.gpx -At the end of the transfer, baud rate is switched to back to the default -of 9600. If connection breaks, the unit stucks at high baud rate, a power +At the end of the transfer, baud rate is switched to back to the default +of 9600. If connection breaks, the unit stucks at high baud rate, a power cycle reverts to original state. @@ -21,7 +21,7 @@ This option does not affect USB transfer. Because this feature uses undocumented Garmin protocols, it may or may -not work on your device. The author reported success with +not work on your device. The author reported success with eTrex Vista, GPSMAP 76s, and GPS V, but it seems likely to be problematic on older units and may be more problematic for writing to the device than reading data from the device. diff --git a/xmldoc/formats/options/garmin-bitscategory.xml b/xmldoc/formats/options/garmin-bitscategory.xml index 5b2c8d668..ee39c4bba 100644 --- a/xmldoc/formats/options/garmin-bitscategory.xml +++ b/xmldoc/formats/options/garmin-bitscategory.xml @@ -1,5 +1,5 @@ - This option is closely related to the 'category' option. While category + This option is closely related to the 'category' option. While category allows you to choose a single category that waypoints should appear in, this options allows you to specify a bitmask to be used for the category. Options may be specified in either decimal or hex. @@ -14,6 +14,6 @@ gpsbabel -i gpx -f PocketQuery.gpx -o garmin,bitcategory=0x8001 -F usb: - + diff --git a/xmldoc/formats/options/garmin-resettime.xml b/xmldoc/formats/options/garmin-resettime.xml index 151a43f7a..4599f8d8a 100644 --- a/xmldoc/formats/options/garmin-resettime.xml +++ b/xmldoc/formats/options/garmin-resettime.xml @@ -1,8 +1,8 @@ This option is experimental and was added to solve a very specific problem. - Certain Garmin units (the original black and white Vista is known to have + Certain Garmin units (the original black and white Vista is known to have this) will sometimes scramble their clock crazy far into the future (like - 2066). When this happens, the GPS itself may or may not work and + 2066). When this happens, the GPS itself may or may not work and later conversations with GPSBabel may fail as the time overflows the documented range. The use of brings the GPS's internal clock back close enough to reality that the GPS itself can then "fix" it when diff --git a/xmldoc/formats/options/garmin-snwhite.xml b/xmldoc/formats/options/garmin-snwhite.xml index 8a2f1987a..423dc52b3 100644 --- a/xmldoc/formats/options/garmin-snwhite.xml +++ b/xmldoc/formats/options/garmin-snwhite.xml @@ -1,2 +1,2 @@ -This options controls whether spaces are allowed in generated +This options controls whether spaces are allowed in generated smart names when using the '-s' option. diff --git a/xmldoc/formats/options/garmin_gpi-alerts.xml b/xmldoc/formats/options/garmin_gpi-alerts.xml index ec142121b..7962fac85 100644 --- a/xmldoc/formats/options/garmin_gpi-alerts.xml +++ b/xmldoc/formats/options/garmin_gpi-alerts.xml @@ -4,7 +4,7 @@ values are in kilometers per hour. - Proximity distance is also supported by GPX, Garmin GDB, OZI Explorer, + Proximity distance is also supported by GPX, Garmin GDB, OZI Explorer, and Universal CSV. diff --git a/xmldoc/formats/options/garmin_gpi-bitmap.xml b/xmldoc/formats/options/garmin_gpi-bitmap.xml index c369a8f08..4c5da44a0 100644 --- a/xmldoc/formats/options/garmin_gpi-bitmap.xml +++ b/xmldoc/formats/options/garmin_gpi-bitmap.xml @@ -5,17 +5,17 @@ If you're starting from images in another format, you may need to use another tool like Gimp or ImageMagick's convert to get the image - into one of the above formats to avoid errors about "Unsupported color + into one of the above formats to avoid errors about "Unsupported color depth". - Not all devices can support all color depths. GPSBabel (and its + Not all devices can support all color depths. GPSBabel (and its developers) have no way of knowing what is supported on any given model so some experimentation may be necessary on your part. It was reported that a Nuvi 3790, for example, will read the POIs only if they use 8BPP. - A color value of 0xFF00FF (blue=255, green=0, red=255), + A color value of 0xFF00FF (blue=255, green=0, red=255), also called "Magenta", can be used for transparent areas. diff --git a/xmldoc/formats/options/garmin_gpi-languagecode.xml b/xmldoc/formats/options/garmin_gpi-languagecode.xml index 87c966edc..fb1217108 100644 --- a/xmldoc/formats/options/garmin_gpi-languagecode.xml +++ b/xmldoc/formats/options/garmin_gpi-languagecode.xml @@ -21,7 +21,7 @@ option to specify which language to use. Example for specifying language with a garmin points of interest dual language file. - gpsbabel -i garmin_gpi,languagecode=EN -f reference/spb_metro_norm.gpi + gpsbabel -i garmin_gpi,languagecode=EN -f reference/spb_metro_norm.gpi could produce the following output: diff --git a/xmldoc/formats/options/garmin_gpi-proximity.xml b/xmldoc/formats/options/garmin_gpi-proximity.xml index bd588457a..cba909bef 100644 --- a/xmldoc/formats/options/garmin_gpi-proximity.xml +++ b/xmldoc/formats/options/garmin_gpi-proximity.xml @@ -25,8 +25,8 @@ - Unit - Description + Unit + Description diff --git a/xmldoc/formats/options/garmin_gpi-sleep.xml b/xmldoc/formats/options/garmin_gpi-sleep.xml index 094fb5f9e..8e63ebde2 100644 --- a/xmldoc/formats/options/garmin_gpi-sleep.xml +++ b/xmldoc/formats/options/garmin_gpi-sleep.xml @@ -1,6 +1,6 @@ - The Garmin units seem to use the creation timestamp of GPI files for internal purposes. - In other words, if you load GPI files with same creation timestamp on your device, + The Garmin units seem to use the creation timestamp of GPI files for internal purposes. + In other words, if you load GPI files with same creation timestamp on your device, strange things will happen, such as having missing or repeated POIs. With the sleep option, GPSBabel waits a given number of seconds after the GPI file was written. diff --git a/xmldoc/formats/options/garmin_gpi-speed.xml b/xmldoc/formats/options/garmin_gpi-speed.xml index 6b909df8f..0c8123958 100644 --- a/xmldoc/formats/options/garmin_gpi-speed.xml +++ b/xmldoc/formats/options/garmin_gpi-speed.xml @@ -23,8 +23,8 @@ - Unit - Description + Unit + Description diff --git a/xmldoc/formats/options/garmin_txt-date.xml b/xmldoc/formats/options/garmin_txt-date.xml index 2f1a3ee59..188eb225d 100644 --- a/xmldoc/formats/options/garmin_txt-date.xml +++ b/xmldoc/formats/options/garmin_txt-date.xml @@ -1,4 +1,4 @@ -This option specifies the input and output format for the date. The format +This option specifies the input and output format for the date. The format is written similarly to those in Windows. An example format is "YYYY/MM/DD". diff --git a/xmldoc/formats/options/garmin_txt-datum.xml b/xmldoc/formats/options/garmin_txt-datum.xml index ce1cadb23..b5c8a5a06 100644 --- a/xmldoc/formats/options/garmin_txt-datum.xml +++ b/xmldoc/formats/options/garmin_txt-datum.xml @@ -1,4 +1,4 @@ -This option specifies the datum to be used on output. Valid values for this +This option specifies the datum to be used on output. Valid values for this option are listed in . diff --git a/xmldoc/formats/options/garmin_txt-grid.xml b/xmldoc/formats/options/garmin_txt-grid.xml index 4db42f886..70365d0a4 100644 --- a/xmldoc/formats/options/garmin_txt-grid.xml +++ b/xmldoc/formats/options/garmin_txt-grid.xml @@ -6,9 +6,9 @@ - # idx - short - file-header + # idx + short + file-header sample diff --git a/xmldoc/formats/options/garmin_txt-time.xml b/xmldoc/formats/options/garmin_txt-time.xml index 145c9a4e3..21675249b 100644 --- a/xmldoc/formats/options/garmin_txt-time.xml +++ b/xmldoc/formats/options/garmin_txt-time.xml @@ -1,4 +1,4 @@ -This option specifies the input and output format for the time. The format +This option specifies the input and output format for the time. The format is written similarly to those in Windows. An example format is "hh:mm:ss xx". diff --git a/xmldoc/formats/options/garmin_txt-utc.xml b/xmldoc/formats/options/garmin_txt-utc.xml index 4c2964e0e..2c4d062ce 100644 --- a/xmldoc/formats/options/garmin_txt-utc.xml +++ b/xmldoc/formats/options/garmin_txt-utc.xml @@ -1,5 +1,5 @@ This option specifies the local time zone to use when writing times. It -is specified as an offset from Universal Coordinated Time (UTC) in hours. +is specified as an offset from Universal Coordinated Time (UTC) in hours. Valid values are from -23 to +23. - + diff --git a/xmldoc/formats/options/gdb-bitscategory.xml b/xmldoc/formats/options/gdb-bitscategory.xml index 32f3815db..a38778130 100644 --- a/xmldoc/formats/options/gdb-bitscategory.xml +++ b/xmldoc/formats/options/gdb-bitscategory.xml @@ -1,5 +1,5 @@ - This option is closely related to the 'category' option. While category + This option is closely related to the 'category' option. While category allows you to choose a single category that waypoints should appear in, this options allows you to specify a bitmask to be used for the category. Options may be specified in either decimal or hex. @@ -14,6 +14,6 @@ gpsbabel -i gpx -f PocketQuery.gpx -o gdb,bitscategory=0x8001 -F foo.gdb - + diff --git a/xmldoc/formats/options/gdb-cat.xml b/xmldoc/formats/options/gdb-cat.xml index 6b876e911..c49aac013 100644 --- a/xmldoc/formats/options/gdb-cat.xml +++ b/xmldoc/formats/options/gdb-cat.xml @@ -1,4 +1,4 @@ -This option specifies the default category for gdb output. It should be a +This option specifies the default category for gdb output. It should be a number from 1 to 16. diff --git a/xmldoc/formats/options/gdb-dropwpt.xml b/xmldoc/formats/options/gdb-dropwpt.xml index fc123f13c..8a56051a1 100644 --- a/xmldoc/formats/options/gdb-dropwpt.xml +++ b/xmldoc/formats/options/gdb-dropwpt.xml @@ -1,5 +1,5 @@ -This option instructs GPSBabel to drop hidden (calculated) points from +This option instructs GPSBabel to drop hidden (calculated) points from routes when creating waypoints. These points are not converted to waypoints, but they are converted to route points. - + diff --git a/xmldoc/formats/options/gdb-roadbook.xml b/xmldoc/formats/options/gdb-roadbook.xml index c1ef6cfe4..c17af7243 100644 --- a/xmldoc/formats/options/gdb-roadbook.xml +++ b/xmldoc/formats/options/gdb-roadbook.xml @@ -1,7 +1,7 @@ - If this option is specified, GPSBabel drops all calculated route points, + If this option is specified, GPSBabel drops all calculated route points, with exception of points with a description (i.e. "Make U-turns until you know where you are."). - The priority of this option is higher than of the and options. + The priority of this option is higher than of the and options. A value of 1 or y overwrites the and settings. @@ -14,6 +14,6 @@ Because gdb internally creates a route AND a waypoint list, you have to drop all waypoints and transform the route into waypoints in order to get a well ordered - html output. We suggest these steps for all waypoint-only formats as html. + html output. We suggest these steps for all waypoint-only formats as html. diff --git a/xmldoc/formats/options/gdb-via.xml b/xmldoc/formats/options/gdb-via.xml index ce782b56a..439d675f9 100644 --- a/xmldoc/formats/options/gdb-via.xml +++ b/xmldoc/formats/options/gdb-via.xml @@ -1,5 +1,5 @@ -This option instructs GPSBabel to drop hidden (calculated) points from +This option instructs GPSBabel to drop hidden (calculated) points from routes. These points are not converted to waypoints or route points. - + diff --git a/xmldoc/formats/options/geo-deficon.xml b/xmldoc/formats/options/geo-deficon.xml index 96d6f27c9..bef014fd1 100644 --- a/xmldoc/formats/options/geo-deficon.xml +++ b/xmldoc/formats/options/geo-deficon.xml @@ -1,10 +1,10 @@ -This option specifies the icon or waypoint type to write for each waypoint on +This option specifies the icon or waypoint type to write for each waypoint on output. -If this option is specified, its value will be used for all waypoints, not -just those that do not already have descriptions. That is, this option +If this option is specified, its value will be used for all waypoints, not +just those that do not already have descriptions. That is, this option overrides any icon description that might be in the input file. diff --git a/xmldoc/formats/options/geojson-compact.xml b/xmldoc/formats/options/geojson-compact.xml index 36bf45414..f4482fb7a 100644 --- a/xmldoc/formats/options/geojson-compact.xml +++ b/xmldoc/formats/options/geojson-compact.xml @@ -1,5 +1,5 @@ - This option, when set, reduces the amount of whitespace in the + This option, when set, reduces the amount of whitespace in the generated GeoJSON. This reduces the size, especially when uncompressed, but reduces the readability to humans. diff --git a/xmldoc/formats/options/globalsat-dump-file.xml b/xmldoc/formats/options/globalsat-dump-file.xml index e4c949fb8..be68763c4 100644 --- a/xmldoc/formats/options/globalsat-dump-file.xml +++ b/xmldoc/formats/options/globalsat-dump-file.xml @@ -1,19 +1,19 @@ The dump-file option is primarily for debugging is module. It lets you provide a file which contains the raw stream of bytes coming from the -device. This is useful for capturing device state to describe to a +device. This is useful for capturing device state to describe to a developer that can't actually access hte physical device as well as mocking the entire device for automated regression testing. -gpsbabel +gpsbabel -i glboalsat,dump-file=gh625xt.bin -f /dev/ttyUSB0 can be used to read the device and store its state in the file gh625xt.bin. That file can then be distributed and someone else can read it with a command line: - gpsbabel + gpsbabel -i globalsat,input-is-dump-file=1 -f gh625xt.bin -o gpx -F test.gpx diff --git a/xmldoc/formats/options/gpssim-split.xml b/xmldoc/formats/options/gpssim-split.xml index 51dad87f7..26a5c9c46 100644 --- a/xmldoc/formats/options/gpssim-split.xml +++ b/xmldoc/formats/options/gpssim-split.xml @@ -1,4 +1,4 @@ -When this option is specified, GPSBabel will split +When this option is specified, GPSBabel will split split the output into multiple files using the output filename as a base. For example, if you specify an output file of 'mytrip', diff --git a/xmldoc/formats/options/gpx-elevprec.xml b/xmldoc/formats/options/gpx-elevprec.xml index 8e08da03f..1b658fb60 100644 --- a/xmldoc/formats/options/gpx-elevprec.xml +++ b/xmldoc/formats/options/gpx-elevprec.xml @@ -3,8 +3,8 @@ This option specifies the number of digits to be used when writing elevation values. Precision is the number of digits after the decimal point. The default precision is 3. We limit the number of places we write to improve the -fidelity when round-tripping elevation, reduce file size, and reduce -silliness in files caused by repeating decimals in insignificant +fidelity when round-tripping elevation, reduce file size, and reduce +silliness in files caused by repeating decimals in insignificant digits. @@ -13,6 +13,6 @@ To achieve precision approaching this limit leveling techniques are required. Precisions beyond this are not currently obtainable. -This value is ignored on read and has no impact on the internal +This value is ignored on read and has no impact on the internal representation of data. diff --git a/xmldoc/formats/options/gpx-garminextensions.xml b/xmldoc/formats/options/gpx-garminextensions.xml index e49e344e5..aa084ce89 100644 --- a/xmldoc/formats/options/gpx-garminextensions.xml +++ b/xmldoc/formats/options/gpx-garminextensions.xml @@ -2,7 +2,7 @@ Write Garmin-specific extensions, when such data is available, to the GPX. Notably, depth, temperature, proximity, display color, ambient temperature, heart rate, and cadence are read when they are available in the source data. - This data can, of course, only be read by GPX readers that know about the + This data can, of course, only be read by GPX readers that know about the Garmin gpxtpx and gpxx extended namespaces. diff --git a/xmldoc/formats/options/gpx-gpxver.xml b/xmldoc/formats/options/gpx-gpxver.xml index 73eac4dfd..e8bb4d08a 100644 --- a/xmldoc/formats/options/gpx-gpxver.xml +++ b/xmldoc/formats/options/gpx-gpxver.xml @@ -1,12 +1,12 @@ -This option specifies the version of the GPX specification to use for +This option specifies the version of the GPX specification to use for output. The default version is 1.0 unless one or more of the input files is GPX 1.1, then it's 1.1. The only other valid value for this option is 1.1. Notice that this is not a full scale XML schema conversion. In particular, -if you have a GPX 1.0 file that has extended namespaces in it (such as a +if you have a GPX 1.0 file that has extended namespaces in it (such as a pocket query from Geocaching.com) just writing it with this option will result in a horribly mangled GPX file as we can't convert the schema data. diff --git a/xmldoc/formats/options/html-encrypt.xml b/xmldoc/formats/options/html-encrypt.xml index 2d7d96091..e81c9e4bd 100644 --- a/xmldoc/formats/options/html-encrypt.xml +++ b/xmldoc/formats/options/html-encrypt.xml @@ -1,3 +1,3 @@ -Use this option to encrypt hints from Groundspeak GPX files. +Use this option to encrypt hints from Groundspeak GPX files. diff --git a/xmldoc/formats/options/html-logs.xml b/xmldoc/formats/options/html-logs.xml index 9e25a13ea..ed91b37a0 100644 --- a/xmldoc/formats/options/html-logs.xml +++ b/xmldoc/formats/options/html-logs.xml @@ -1,3 +1,3 @@ -Use this option to include Groundspeak cache logs in the created document. +Use this option to include Groundspeak cache logs in the created document. diff --git a/xmldoc/formats/options/ignrando-index.xml b/xmldoc/formats/options/ignrando-index.xml index f61f0e790..155051443 100644 --- a/xmldoc/formats/options/ignrando-index.xml +++ b/xmldoc/formats/options/ignrando-index.xml @@ -1,7 +1,7 @@ -Because the format supports only one track, this option may be used -on output to select a single track from a collection of -tracks read from a more expressive format. If you have, say, a +Because the format supports only one track, this option may be used +on output to select a single track from a collection of +tracks read from a more expressive format. If you have, say, a gpx file that contains two tracks, you may use this option to write them one at a time to individual files. diff --git a/xmldoc/formats/options/igo8-tracknum.xml b/xmldoc/formats/options/igo8-tracknum.xml index fe2ed760d..00832a80d 100644 --- a/xmldoc/formats/options/igo8-tracknum.xml +++ b/xmldoc/formats/options/igo8-tracknum.xml @@ -1,7 +1,7 @@ This option isn't entirely clear. It appears to be a unique number for each track that is used for coloring on the main display. So if you - want two tracks to have different colors, set the track numbers to + want two tracks to have different colors, set the track numbers to different values. diff --git a/xmldoc/formats/options/itracku-backup.xml b/xmldoc/formats/options/itracku-backup.xml index cf5ab5e0b..36e6c4658 100644 --- a/xmldoc/formats/options/itracku-backup.xml +++ b/xmldoc/formats/options/itracku-backup.xml @@ -1,4 +1,4 @@ -Specifies a backup file for the binary logger data. New waypoints from the logger will be appended to an existing +Specifies a backup file for the binary logger data. New waypoints from the logger will be appended to an existing backup file. This allows you to create "endless" binary logger files which, for example, could contain the waypoint data of a whole year. The backup file can be read with gpsbabel by using the itracku format. diff --git a/xmldoc/formats/options/itracku-new.xml b/xmldoc/formats/options/itracku-new.xml index 300b3d8b7..763e2389b 100644 --- a/xmldoc/formats/options/itracku-new.xml +++ b/xmldoc/formats/options/itracku-new.xml @@ -1,10 +1,10 @@ -Will only pass waypoints along to filters and output formats that are not new, i.e. that are not already stored in the +Will only pass waypoints along to filters and output formats that are not new, i.e. that are not already stored in the backup file. This option can only be used with the backup option. -Using this option allows you to output the waypoints of your latest trip with gpsbabel while keeping an endless log of all waypoints +Using this option allows you to output the waypoints of your latest trip with gpsbabel while keeping an endless log of all waypoints in the backup file. - Download from the data logger and append the new logger data to a backup file. Output only the new + <title>Download from the data logger and append the new logger data to a backup file. Output only the new waypoints. gpsbabel -i itracku,auto,backup=itracku.bak,new -f dummy -o gpx -F out.gpx diff --git a/xmldoc/formats/options/kml-line_color.xml b/xmldoc/formats/options/kml-line_color.xml index 33892c4c7..3bbc62cfe 100644 --- a/xmldoc/formats/options/kml-line_color.xml +++ b/xmldoc/formats/options/kml-line_color.xml @@ -1,5 +1,5 @@ -This option specifies the line color as a hexadecimal number in +This option specifies the line color as a hexadecimal number in AABBGGRR format, where A is alpha, B is blue, G is green, and R is red. diff --git a/xmldoc/formats/options/kml-lines.xml b/xmldoc/formats/options/kml-lines.xml index fbe2dafaa..271fd521d 100644 --- a/xmldoc/formats/options/kml-lines.xml +++ b/xmldoc/formats/options/kml-lines.xml @@ -1,6 +1,6 @@ When this option is nonzero, GPSBabel draws lines between points in tracks and routes. The default value for this option is 1, which causes -lines to be drawn by default. To disable line-drawing, specify +lines to be drawn by default. To disable line-drawing, specify . diff --git a/xmldoc/formats/options/kml-prec.xml b/xmldoc/formats/options/kml-prec.xml index c0e09e6ae..5fd64d52e 100644 --- a/xmldoc/formats/options/kml-prec.xml +++ b/xmldoc/formats/options/kml-prec.xml @@ -3,17 +3,17 @@ This option specifies the number of digits to be used when writing coordinate values. Precision is the number of digits after the decimal point. The default precision is 6. We limit the number of places we write to improve the -fidelity when round-tripping thata, reduce file size, and reduce -silliness in files caused by repeating decimals in insignificant +fidelity when round-tripping thata, reduce file size, and reduce +silliness in files caused by repeating decimals in insignificant digits. -As a guideline, at the equator, five decimal places is about 1.1 m, +As a guideline, at the equator, five decimal places is about 1.1 m, placing it below the accuracy of commodity consumer GPS gear. Six places is 0.11 m, achievable via surveyor grade and differential corrected GPS. Seven is 11 millimeters. -This value is ignored on read and has no impact on the internal +This value is ignored on read and has no impact on the internal representation of data. diff --git a/xmldoc/formats/options/kml-rotate_colors.xml b/xmldoc/formats/options/kml-rotate_colors.xml index 4e3ef0e64..a6e9831f4 100644 --- a/xmldoc/formats/options/kml-rotate_colors.xml +++ b/xmldoc/formats/options/kml-rotate_colors.xml @@ -3,6 +3,6 @@ With this option GPSBabel uses different colors for each track or route. If this option is used without a value then the colors are automatically selected such that the spectrum will be rotated through once for all the tracks and once for all the routes. If this option is used with a positive value then the value is interpreted as the number of degrees -in the color circle between adjacent tracks or routes. +in the color circle between adjacent tracks or routes. This option takes precedence over line_color. diff --git a/xmldoc/formats/options/kml-trackdirection.xml b/xmldoc/formats/options/kml-trackdirection.xml index 6449dd03d..51371e359 100644 --- a/xmldoc/formats/options/kml-trackdirection.xml +++ b/xmldoc/formats/options/kml-trackdirection.xml @@ -1,4 +1,4 @@ - If set, this options creates directional icons for trackpoints. Arrows + If set, this options creates directional icons for trackpoints. Arrows will show the direction of travel on drawn tracks and routes. diff --git a/xmldoc/formats/options/kml-units.xml b/xmldoc/formats/options/kml-units.xml index 733e74bb8..8d55ba6c2 100644 --- a/xmldoc/formats/options/kml-units.xml +++ b/xmldoc/formats/options/kml-units.xml @@ -1,5 +1,5 @@ -Units is a simple option. Specify 's' for "statute" (miles, feet, and +Units is a simple option. Specify 's' for "statute" (miles, feet, and other things that don't sensibly convert to each other, but are craved by Americans), 'm' for "metric", 'n' for "nautical" or 'a' for "aviation". Default is 's'. diff --git a/xmldoc/formats/options/lowranceusr-wversion.xml b/xmldoc/formats/options/lowranceusr-wversion.xml index 03e0eeb1a..f27d352b3 100644 --- a/xmldoc/formats/options/lowranceusr-wversion.xml +++ b/xmldoc/formats/options/lowranceusr-wversion.xml @@ -3,7 +3,7 @@ it is currently only able to generate USR format 2, 3, or 4 due to the lack of detailed information on some of the data contained in the other formats. - + By default, GPSBabel will generate USR version 2 data if the output format is specified as lowranceusr. @@ -24,7 +24,7 @@ is exactly the same as USR file format that adds waypoint depth. Lowrance recommends that this USR version be used when transferring user data to systems such as LMS, LCX, and so on. Specify "3" to output USR version 3 data - on write. + on write. diff --git a/xmldoc/formats/options/magellan-maxcmts.xml b/xmldoc/formats/options/magellan-maxcmts.xml index 1c46dd108..70104bbbe 100644 --- a/xmldoc/formats/options/magellan-maxcmts.xml +++ b/xmldoc/formats/options/magellan-maxcmts.xml @@ -6,7 +6,7 @@ be sent to the unit. Magellan receivers allow a maximum of 200 waypoint comments. Unfortunately, DirectRoute uses waypoint comments to provide next turn directions for navigation pop-ups and that comes from that pool of 200 comments. It -is therefore sometimes convenient to limit the number of waypoint +is therefore sometimes convenient to limit the number of waypoint comments written to the receiver. For example, a geocacher might want to upload 400 waypoints, but only 190 with comments so that DirectRoute could provide driving directions for the next ten turns. diff --git a/xmldoc/formats/options/magellan1-baud.xml b/xmldoc/formats/options/magellan1-baud.xml index 0682faa0a..c6370d684 100644 --- a/xmldoc/formats/options/magellan1-baud.xml +++ b/xmldoc/formats/options/magellan1-baud.xml @@ -1,6 +1,6 @@ This option causes GPSBabel to use the given baud rate for serial - communications. It must match the given baud rate on the receiver. The + communications. It must match the given baud rate on the receiver. The default value matches the default on the receiver, 4800. diff --git a/xmldoc/formats/options/magellan1-maxcmts.xml b/xmldoc/formats/options/magellan1-maxcmts.xml index 1c46dd108..70104bbbe 100644 --- a/xmldoc/formats/options/magellan1-maxcmts.xml +++ b/xmldoc/formats/options/magellan1-maxcmts.xml @@ -6,7 +6,7 @@ be sent to the unit. Magellan receivers allow a maximum of 200 waypoint comments. Unfortunately, DirectRoute uses waypoint comments to provide next turn directions for navigation pop-ups and that comes from that pool of 200 comments. It -is therefore sometimes convenient to limit the number of waypoint +is therefore sometimes convenient to limit the number of waypoint comments written to the receiver. For example, a geocacher might want to upload 400 waypoints, but only 190 with comments so that DirectRoute could provide driving directions for the next ten turns. diff --git a/xmldoc/formats/options/magellan1-noack.xml b/xmldoc/formats/options/magellan1-noack.xml index 6a136c47e..8727166ec 100644 --- a/xmldoc/formats/options/magellan1-noack.xml +++ b/xmldoc/formats/options/magellan1-noack.xml @@ -7,11 +7,11 @@ handshake that is used to ensure the integrity of the data transfer. Certain firmware versions have problems handling this which makes transfers unnecessarily slow. Transfers on all units at high serial speeds are also -severely restricted by this process. +severely restricted by this process. In controlled environments (good cables, low electrical noise, receiving from the unit, not doing donuts with the unit set to "track up" at a 150 -mile scale with 500 waypoints on the screen) it is sometimes useful to +mile scale with 500 waypoints on the screen) it is sometimes useful to release that safety belt by using the "noack" suboption. diff --git a/xmldoc/formats/options/magellan1-nukewpt.xml b/xmldoc/formats/options/magellan1-nukewpt.xml index 5ca891611..57de6cc86 100644 --- a/xmldoc/formats/options/magellan1-nukewpt.xml +++ b/xmldoc/formats/options/magellan1-nukewpt.xml @@ -4,7 +4,7 @@ This option erases all waypoints in the receiver before doing a transfer. This is a convenient option to use in automated processes where you want to ensure the units starts with a clean state before sending waypoints to -it. Using this option on transmit is a better idea than doing it on +it. Using this option on transmit is a better idea than doing it on receive since the latter would erase all the waypoints before asking the unit to send all the waypoints. diff --git a/xmldoc/formats/options/magellanx-maxcmts.xml b/xmldoc/formats/options/magellanx-maxcmts.xml index 1c46dd108..70104bbbe 100644 --- a/xmldoc/formats/options/magellanx-maxcmts.xml +++ b/xmldoc/formats/options/magellanx-maxcmts.xml @@ -6,7 +6,7 @@ be sent to the unit. Magellan receivers allow a maximum of 200 waypoint comments. Unfortunately, DirectRoute uses waypoint comments to provide next turn directions for navigation pop-ups and that comes from that pool of 200 comments. It -is therefore sometimes convenient to limit the number of waypoint +is therefore sometimes convenient to limit the number of waypoint comments written to the receiver. For example, a geocacher might want to upload 400 waypoints, but only 190 with comments so that DirectRoute could provide driving directions for the next ten turns. diff --git a/xmldoc/formats/options/miniHomer-Bar.xml b/xmldoc/formats/options/miniHomer-Bar.xml index 67151f40d..6eb54e27b 100644 --- a/xmldoc/formats/options/miniHomer-Bar.xml +++ b/xmldoc/formats/options/miniHomer-Bar.xml @@ -1,8 +1,8 @@ - The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar". - You can program the location of each either by a keypress on the device (which uses the actual position) + The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar". + You can program the location of each either by a keypress on the device (which uses the actual position) or with GPSBabel (which lets you use any position) - You can set the location of "Bar" with the 'Bar' option. Use ':' as the delimiter between latitude, longitude and altitude. + You can set the location of "Bar" with the 'Bar' option. Use ':' as the delimiter between latitude, longitude and altitude. You can leave altitude out, in which case it is assumed to be zero. Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it. @@ -13,7 +13,7 @@ Sets the Bar symbols' latitude to 38.99809N longitude to 86.34662W and altitude to 0m. - If you select the Bar symbol on miniHomer, the display will show the direction and distance to + If you select the Bar symbol on miniHomer, the display will show the direction and distance to this location as soon as it has a satellite fix. diff --git a/xmldoc/formats/options/miniHomer-Boat.xml b/xmldoc/formats/options/miniHomer-Boat.xml index ba5cbc5b4..9d26fb393 100644 --- a/xmldoc/formats/options/miniHomer-Boat.xml +++ b/xmldoc/formats/options/miniHomer-Boat.xml @@ -1,8 +1,8 @@ - The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar". - You can program the location of each either by a keypress on the device (which uses the actual position) + The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar". + You can program the location of each either by a keypress on the device (which uses the actual position) or with GPSBabel (which lets you use any position) - You can set the location of "Boat" with the 'Boat' option. Use ':' as the delimiter between latitude, longitude and altitude. + You can set the location of "Boat" with the 'Boat' option. Use ':' as the delimiter between latitude, longitude and altitude. You can leave altitude out, in which case it is assumed to be zero. Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it. @@ -13,7 +13,7 @@ Sets the Boat symbols' latitude to 32.29287N longitude to 64.77527E and altitude to 0m. - If you select the Home symbol on miniHomer, the display will show the direction and distance to + If you select the Home symbol on miniHomer, the display will show the direction and distance to this location as soon as it has a satellite fix. diff --git a/xmldoc/formats/options/miniHomer-Car.xml b/xmldoc/formats/options/miniHomer-Car.xml index 10d8f8868..38690b9e4 100644 --- a/xmldoc/formats/options/miniHomer-Car.xml +++ b/xmldoc/formats/options/miniHomer-Car.xml @@ -1,8 +1,8 @@ - The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar". - You can program the location of each either by a keypress on the device (which uses the actual position) + The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar". + You can program the location of each either by a keypress on the device (which uses the actual position) or with GPSBabel (which lets you use any position) - You can set the location of "Car" with the 'Car' option. Use ':' as the delimiter between latitude, longitude and altitude. + You can set the location of "Car" with the 'Car' option. Use ':' as the delimiter between latitude, longitude and altitude. You can leave altitude out, in which case it is assumed to be zero. Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it. @@ -13,7 +13,7 @@ Sets the Car symbols' latitude to 25.272309S longitude to 153.235330E and altitude to 0m. - If you select the Car symbol on miniHomer, the display will show the direction and distance to + If you select the Car symbol on miniHomer, the display will show the direction and distance to this location as soon as it has a satellite fix. diff --git a/xmldoc/formats/options/miniHomer-Heart.xml b/xmldoc/formats/options/miniHomer-Heart.xml index 9bed7327f..3c07af1da 100644 --- a/xmldoc/formats/options/miniHomer-Heart.xml +++ b/xmldoc/formats/options/miniHomer-Heart.xml @@ -1,8 +1,8 @@ - The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar". - You can program the location of each either by a keypress on the device (which uses the actual position) + The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar". + You can program the location of each either by a keypress on the device (which uses the actual position) or with GPSBabel (which lets you use any position) - You can set the location of "Heart" with the 'Heart' option. Use ':' as the delimiter between latitude, longitude and altitude. + You can set the location of "Heart" with the 'Heart' option. Use ':' as the delimiter between latitude, longitude and altitude. You can leave altitude out, in which case it is assumed to be zero. Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it. @@ -13,7 +13,7 @@ Sets the Heart symbols' latitude to 36.1269N longitude to 115.1698W and altitude to 0m. - If you select the Heart symbol on miniHomer, the display will show the direction and distance to + If you select the Heart symbol on miniHomer, the display will show the direction and distance to this location as soon as it has a satellite fix. diff --git a/xmldoc/formats/options/miniHomer-Home.xml b/xmldoc/formats/options/miniHomer-Home.xml index ada385885..c583063b8 100644 --- a/xmldoc/formats/options/miniHomer-Home.xml +++ b/xmldoc/formats/options/miniHomer-Home.xml @@ -1,8 +1,8 @@ - The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar". - You can program the location of each either by a keypress on the device (which uses the actual position) + The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar". + You can program the location of each either by a keypress on the device (which uses the actual position) or with GPSBabel (which lets you use any position) - You can set the location of "Home" with the 'Home' option. Use ':' as the delimiter between latitude, longitude and altitude. + You can set the location of "Home" with the 'Home' option. Use ':' as the delimiter between latitude, longitude and altitude. You can leave altitude out, in which case it is assumed to be zero. Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it. @@ -13,7 +13,7 @@ Sets the Home symbols' latitude to 3.066667S longitude to 37.359167E and altitude to 5895m. - If you select the Home symbol on miniHomer, the display will show the direction and distance to + If you select the Home symbol on miniHomer, the display will show the direction and distance to this location as soon as it has a satellite fix. diff --git a/xmldoc/formats/options/miniHomer-initbaud.xml b/xmldoc/formats/options/miniHomer-initbaud.xml index 43de781a7..5b99e8e35 100644 --- a/xmldoc/formats/options/miniHomer-initbaud.xml +++ b/xmldoc/formats/options/miniHomer-initbaud.xml @@ -1,5 +1,5 @@ -This function is identical to the init-baud file function of skytraq module. +This function is identical to the init-baud file function of skytraq module. The "initbaud" option might be helpful if autodetection fails or takes too long. With this option you can tell GPSBabel the baud rate the device is currently set to. In contrast, the option "baud" specifies diff --git a/xmldoc/formats/options/miniHomer-last-sector.xml b/xmldoc/formats/options/miniHomer-last-sector.xml index 836f46e23..ffe30b687 100644 --- a/xmldoc/formats/options/miniHomer-last-sector.xml +++ b/xmldoc/formats/options/miniHomer-last-sector.xml @@ -2,4 +2,4 @@ encountered. We observed that sometimes the device doesn't report the correct number of used sectors, which confuses the Windows software, so that it might not get all trackpoints. -In contrast, our algorithm ensures that everything is being read (please report if it doesn't work for you). +In contrast, our algorithm ensures that everything is being read (please report if it doesn't work for you). diff --git a/xmldoc/formats/options/mmo-ver.xml b/xmldoc/formats/options/mmo-ver.xml index b17c3785d..9266dcace 100644 --- a/xmldoc/formats/options/mmo-ver.xml +++ b/xmldoc/formats/options/mmo-ver.xml @@ -1,8 +1,8 @@ -Two major strains of Mobile Mapper files have been identified in the wild. Version 17 is reported as "Memory Map OS Edition 2004, Versio 4.2.3 Build 432" and version 18 is used by the large majority of current files. We can read either and when writing, we write version 18 by default. +Two major strains of Mobile Mapper files have been identified in the wild. Version 17 is reported as "Memory Map OS Edition 2004, Versio 4.2.3 Build 432" and version 18 is used by the large majority of current files. We can read either and when writing, we write version 18 by default. -If you have a particularly old Mobile Mapper installation, it may complain "This file was created with a newer version of the Software" when reading our output.You can get around this if force GPSBabel to create the old format with this option. +If you have a particularly old Mobile Mapper installation, it may complain "This file was created with a newer version of the Software" when reading our output.You can get around this if force GPSBabel to create the old format with this option. Forcing creation of old Mobile Mapper files diff --git a/xmldoc/formats/options/mtk_locus-download.xml b/xmldoc/formats/options/mtk_locus-download.xml index 60bbd0597..c6186589a 100644 --- a/xmldoc/formats/options/mtk_locus-download.xml +++ b/xmldoc/formats/options/mtk_locus-download.xml @@ -1,5 +1,5 @@ -This option processes a set of Locus fixes, by downloading it from an +This option processes a set of Locus fixes, by downloading it from an attached USB device or by reading records stored in a normal file. -You might want to disable this option if all you want to do is erase the memory +You might want to disable this option if all you want to do is erase the memory or display the device status. Downloading a large dataset can take several minutes and while that is happening no other device commands can be executed. diff --git a/xmldoc/formats/options/netstumbler-nseicon.xml b/xmldoc/formats/options/netstumbler-nseicon.xml index 4a6d622e8..cc5b49af9 100644 --- a/xmldoc/formats/options/netstumbler-nseicon.xml +++ b/xmldoc/formats/options/netstumbler-nseicon.xml @@ -1,4 +1,4 @@ -This option specifies the name of the icon to use for +This option specifies the name of the icon to use for non-stealth, encrypted access points. diff --git a/xmldoc/formats/options/netstumbler-nsneicon.xml b/xmldoc/formats/options/netstumbler-nsneicon.xml index bf0f7cc35..d1fe81284 100644 --- a/xmldoc/formats/options/netstumbler-nsneicon.xml +++ b/xmldoc/formats/options/netstumbler-nsneicon.xml @@ -1,4 +1,4 @@ -This option specifies the name of the icon to use for +This option specifies the name of the icon to use for non-stealth, non-encrypted access points. diff --git a/xmldoc/formats/options/netstumbler-seicon.xml b/xmldoc/formats/options/netstumbler-seicon.xml index 3f0accbdc..536d6ecfb 100644 --- a/xmldoc/formats/options/netstumbler-seicon.xml +++ b/xmldoc/formats/options/netstumbler-seicon.xml @@ -1,4 +1,4 @@ -This option specifies the name of the icon to use for +This option specifies the name of the icon to use for stealth, encrypted access points. diff --git a/xmldoc/formats/options/netstumbler-sneicon.xml b/xmldoc/formats/options/netstumbler-sneicon.xml index 174ad2b32..dfeb3e1db 100644 --- a/xmldoc/formats/options/netstumbler-sneicon.xml +++ b/xmldoc/formats/options/netstumbler-sneicon.xml @@ -1,4 +1,4 @@ -This option specifies the name of the icon to use for +This option specifies the name of the icon to use for stealth, non-encrypted access points. diff --git a/xmldoc/formats/options/nmea-append_positioning.xml b/xmldoc/formats/options/nmea-append_positioning.xml index 1706e47db..0f97797cd 100644 --- a/xmldoc/formats/options/nmea-append_positioning.xml +++ b/xmldoc/formats/options/nmea-append_positioning.xml @@ -1,5 +1,5 @@ - When writing NMEA realtime positioning data, append to the + When writing NMEA realtime positioning data, append to the output file instead of truncating it on each successive position fix. diff --git a/xmldoc/formats/options/nmea-date.xml b/xmldoc/formats/options/nmea-date.xml index 81467a8c9..e007e5a03 100644 --- a/xmldoc/formats/options/nmea-date.xml +++ b/xmldoc/formats/options/nmea-date.xml @@ -1,9 +1,9 @@ -On input, track points with times but no dates will have this date applied. +On input, track points with times but no dates will have this date applied. This is necessary because some NMEA sentences contain times but no dates. If -this option is not specified and the date cannot be determined from one or +this option is not specified and the date cannot be determined from one or more of the available NMEA sentences, the tracks will be discarded. diff --git a/xmldoc/formats/options/nmea-gisteq.xml b/xmldoc/formats/options/nmea-gisteq.xml index 259529400..d1e450265 100644 --- a/xmldoc/formats/options/nmea-gisteq.xml +++ b/xmldoc/formats/options/nmea-gisteq.xml @@ -1,6 +1,6 @@ - This option writes the Gisteq format - which has the extension of .GPS - - to allow third-party GPS hardware with the Gisteq PhotoTrackr software. + This option writes the Gisteq format - which has the extension of .GPS - + to allow third-party GPS hardware with the Gisteq PhotoTrackr software. The Gisteq PhotoTrackr is a GPS data logger hardware and software package @@ -9,9 +9,9 @@ digital photos with the timestamps in the tracking data. In doing so, the software plots the locations of the photos using Google Maps. The logging format used by the Gisteq hardware is very close to NMEA format, but with a - few small quirks. + few small quirks. -More information can be found at the +More information can be found at the Gisteq site. diff --git a/xmldoc/formats/options/nmea-gpgga.xml b/xmldoc/formats/options/nmea-gpgga.xml index 2b89b5072..86385847d 100644 --- a/xmldoc/formats/options/nmea-gpgga.xml +++ b/xmldoc/formats/options/nmea-gpgga.xml @@ -1,6 +1,6 @@ -This option tells GPSBabel whether to read (on input) or write (on output) -GPGGA sentences. The default is to read or write GPGGA sentences. To +This option tells GPSBabel whether to read (on input) or write (on output) +GPGGA sentences. The default is to read or write GPGGA sentences. To disable GPGGA sentences, specify . diff --git a/xmldoc/formats/options/nmea-gpgsa.xml b/xmldoc/formats/options/nmea-gpgsa.xml index 40412dd84..277556079 100644 --- a/xmldoc/formats/options/nmea-gpgsa.xml +++ b/xmldoc/formats/options/nmea-gpgsa.xml @@ -1,12 +1,12 @@ -This option tells GPSBabel whether to read (on input) or write (on output) -GPGSA sentences. The default is to read or write GPGSA sentences. To +This option tells GPSBabel whether to read (on input) or write (on output) +GPGSA sentences. The default is to read or write GPGSA sentences. To disable GPGSA sentences, specify . GPGSA sentences contain information on the quality of the positional fix and the individual satellites from which it was derived. However, GPSBabel -neither reads nor writes the individual satellite data. On input, the +neither reads nor writes the individual satellite data. On input, the satellite fields are ignored and on output they are left blank. diff --git a/xmldoc/formats/options/nmea-gprmc.xml b/xmldoc/formats/options/nmea-gprmc.xml index a53fab446..78de6e63c 100644 --- a/xmldoc/formats/options/nmea-gprmc.xml +++ b/xmldoc/formats/options/nmea-gprmc.xml @@ -1,11 +1,11 @@ -This option tells GPSBabel whether to read (on input) or write (on output) -GPRMC sentences. The default is to read or write GPRMC sentences. To +This option tells GPSBabel whether to read (on input) or write (on output) +GPRMC sentences. The default is to read or write GPRMC sentences. To disable GPRMC sentences, specify . -GPRMC sentences contain the "recommended minimum" positional information, -including date and time, heading, and velocity. Note that they do not +GPRMC sentences contain the "recommended minimum" positional information, +including date and time, heading, and velocity. Note that they do not include altitude. For altitude, you will have to include GPGGA sentences. diff --git a/xmldoc/formats/options/nmea-gpvtg.xml b/xmldoc/formats/options/nmea-gpvtg.xml index 85d587517..3680b7f20 100644 --- a/xmldoc/formats/options/nmea-gpvtg.xml +++ b/xmldoc/formats/options/nmea-gpvtg.xml @@ -1,11 +1,11 @@ -This option tells GPSBabel whether to read (on input) or write (on output) -GPVTG sentences. The default is to read or write GPVTG sentences. To +This option tells GPSBabel whether to read (on input) or write (on output) +GPVTG sentences. The default is to read or write GPVTG sentences. To disable GPVTG sentences, specify . GPVTG sentences contain information about the heading and the speed at the -time of the fix. They do not contain any location information; for that +time of the fix. They do not contain any location information; for that you will need either or both of GPGGA or GPRMC. diff --git a/xmldoc/formats/options/nmea-pause.xml b/xmldoc/formats/options/nmea-pause.xml index 88112a5db..2d805bb15 100644 --- a/xmldoc/formats/options/nmea-pause.xml +++ b/xmldoc/formats/options/nmea-pause.xml @@ -1,6 +1,6 @@ This option tells GPSBabel to pause between individual track records when -used on output. This may be used with appropriate external software or +used on output. This may be used with appropriate external software or hardware to simulate a GPS receiver for testing purposes. On Unix, for example, you may use a named pipe to feed the output from GPSBabel to gpsd. @@ -10,22 +10,22 @@ either a whole number of seconds or a fraction (e.g. 0.5 for a 1/2 second pause between trackpoints.) -If this option is specified with a negative value, the time between adjacent +If this option is specified with a negative value, the time between adjacent trackpoints will be computed and used for the length of the pause. That is, -if your trackpoints are 5 seconds apart, GPSBabel will pause 5 seconds +if your trackpoints are 5 seconds apart, GPSBabel will pause 5 seconds between trackpoints. -Note that very long tracks may be subject to clock drift, as GPSBabel does -not take into account the amount of time it may take to write the NMEA +Note that very long tracks may be subject to clock drift, as GPSBabel does +not take into account the amount of time it may take to write the NMEA sentences. Also, there is no guarantee that it will pause for exactly the -specified number of seconds between samples; different operating systems +specified number of seconds between samples; different operating systems will allow greater or lesser precision for timers, so actual precision may be as much as plus or minus 100 milliseconds. -If you are using this option with compressed or simplified tracks from -your handheld GPS receiver, you might find the +If you are using this option with compressed or simplified tracks from +your handheld GPS receiver, you might find the interpolate filter useful. diff --git a/xmldoc/formats/options/nmea-snlen.xml b/xmldoc/formats/options/nmea-snlen.xml index 36e9c734b..d14ee7430 100644 --- a/xmldoc/formats/options/nmea-snlen.xml +++ b/xmldoc/formats/options/nmea-snlen.xml @@ -1,6 +1,6 @@ -This option specifies the maximum length to be used for waypoint names in -the GPWPL sentence. Longer names will be shortened to no more than this +This option specifies the maximum length to be used for waypoint names in +the GPWPL sentence. Longer names will be shortened to no more than this length, but all waypoint names will remain unique. diff --git a/xmldoc/formats/options/osm-created_by.xml b/xmldoc/formats/options/osm-created_by.xml index ce5b270d2..29615d580 100644 --- a/xmldoc/formats/options/osm-created_by.xml +++ b/xmldoc/formats/options/osm-created_by.xml @@ -1,7 +1,7 @@ Use this value as custom created_by value in an OSM file. -With this option, the given string is added as the 'created_by' field in +With this option, the given string is added as the 'created_by' field in all the created nodes and ways. diff --git a/xmldoc/formats/options/ozi-pack.xml b/xmldoc/formats/options/ozi-pack.xml index 1586c74cb..ae73bad93 100644 --- a/xmldoc/formats/options/ozi-pack.xml +++ b/xmldoc/formats/options/ozi-pack.xml @@ -1,5 +1,5 @@ - In normal case GPSBabel creates for each track a separate file (track.plt, track-1.plt, ...). + In normal case GPSBabel creates for each track a separate file (track.plt, track-1.plt, ...). With this option all tracks will be written into one file. A '1' in the third field of the trackpoint record signals the beginning of a new track. diff --git a/xmldoc/formats/options/ozi-proximity.xml b/xmldoc/formats/options/ozi-proximity.xml index 184890366..492954431 100644 --- a/xmldoc/formats/options/ozi-proximity.xml +++ b/xmldoc/formats/options/ozi-proximity.xml @@ -1,4 +1,4 @@ - This option, specified in meters, allows you to set the proximity of + This option, specified in meters, allows you to set the proximity of written waypoints. diff --git a/xmldoc/formats/options/palmdoc-bookmarks_short.xml b/xmldoc/formats/options/palmdoc-bookmarks_short.xml index b1c22efb5..e33d9bbe3 100644 --- a/xmldoc/formats/options/palmdoc-bookmarks_short.xml +++ b/xmldoc/formats/options/palmdoc-bookmarks_short.xml @@ -6,4 +6,4 @@ the short name for the waypoint, specify this option. This is particularly useful when used in combination with the 'sort' filter. - + diff --git a/xmldoc/formats/options/palmdoc-dbname.xml b/xmldoc/formats/options/palmdoc-dbname.xml index 626baaa86..ef47a3a2d 100644 --- a/xmldoc/formats/options/palmdoc-dbname.xml +++ b/xmldoc/formats/options/palmdoc-dbname.xml @@ -1,5 +1,5 @@ This option specifies the internal name for the document. This is the name that appears in your document reader, not the name of the file that is created -on your computer. +on your computer. diff --git a/xmldoc/formats/options/palmdoc-encrypt.xml b/xmldoc/formats/options/palmdoc-encrypt.xml index 2d7d96091..e81c9e4bd 100644 --- a/xmldoc/formats/options/palmdoc-encrypt.xml +++ b/xmldoc/formats/options/palmdoc-encrypt.xml @@ -1,3 +1,3 @@ -Use this option to encrypt hints from Groundspeak GPX files. +Use this option to encrypt hints from Groundspeak GPX files. diff --git a/xmldoc/formats/options/palmdoc-logs.xml b/xmldoc/formats/options/palmdoc-logs.xml index 9e25a13ea..ed91b37a0 100644 --- a/xmldoc/formats/options/palmdoc-logs.xml +++ b/xmldoc/formats/options/palmdoc-logs.xml @@ -1,3 +1,3 @@ -Use this option to include Groundspeak cache logs in the created document. +Use this option to include Groundspeak cache logs in the created document. diff --git a/xmldoc/formats/options/palmdoc-nosep.xml b/xmldoc/formats/options/palmdoc-nosep.xml index 75e79abf7..c02bbcbb8 100644 --- a/xmldoc/formats/options/palmdoc-nosep.xml +++ b/xmldoc/formats/options/palmdoc-nosep.xml @@ -1,3 +1,3 @@ -To suppress the dashed lines between waypoints, use this option. +To suppress the dashed lines between waypoints, use this option. diff --git a/xmldoc/formats/options/pathaway-date.xml b/xmldoc/formats/options/pathaway-date.xml index e505b5eb7..c45f6be83 100644 --- a/xmldoc/formats/options/pathaway-date.xml +++ b/xmldoc/formats/options/pathaway-date.xml @@ -1,4 +1,4 @@ -This option specifies the input and output format for the date. The format +This option specifies the input and output format for the date. The format is written similarly to those in Windows. An example format is "YYMMDD". diff --git a/xmldoc/formats/options/saroute-controls.xml b/xmldoc/formats/options/saroute-controls.xml index e532c0c6d..3469f4845 100644 --- a/xmldoc/formats/options/saroute-controls.xml +++ b/xmldoc/formats/options/saroute-controls.xml @@ -7,4 +7,4 @@ named 'control points' containing just the control points in order. Note that if your goal is to create an arc or other CSV file, you should use 'none' (or not use this option, which is the same thing.) - + diff --git a/xmldoc/formats/options/saroute-split.xml b/xmldoc/formats/options/saroute-split.xml index e83fd4d17..13c2d797d 100644 --- a/xmldoc/formats/options/saroute-split.xml +++ b/xmldoc/formats/options/saroute-split.xml @@ -2,4 +2,4 @@ routes for each street, creating a new route at each turn point. For obvious reasons, 'split' cannot be used at the same time as the 'turns_only' or 'turns_important' options. - + diff --git a/xmldoc/formats/options/saroute-times.xml b/xmldoc/formats/options/saroute-times.xml index 857b3d3ce..77e95c713 100644 --- a/xmldoc/formats/options/saroute-times.xml +++ b/xmldoc/formats/options/saroute-times.xml @@ -2,4 +2,4 @@ it were a track, synthesizing times starting from the current time, using the estimated travel times specified in your route file (you can change your travel speeds in the DeLorme product you used to create the route file.) - + diff --git a/xmldoc/formats/options/saroute-turns_important.xml b/xmldoc/formats/options/saroute-turns_important.xml index 82b793a09..ddf960d33 100644 --- a/xmldoc/formats/options/saroute-turns_important.xml +++ b/xmldoc/formats/options/saroute-turns_important.xml @@ -3,4 +3,4 @@ conjunction with the 'simplify' filter. It ensures that the route simplification process will remove the points corresponding to turns only after it has removed all other route points. - + diff --git a/xmldoc/formats/options/saroute-turns_only.xml b/xmldoc/formats/options/saroute-turns_only.xml index 1c35dc5d8..aced4c411 100644 --- a/xmldoc/formats/options/saroute-turns_only.xml +++ b/xmldoc/formats/options/saroute-turns_only.xml @@ -1,4 +1,4 @@ This option causes GPSBabel to read only the waypoints associated with named turns. This should create a list of waypoints that correspond to the itinerary from Street Atlas. - + diff --git a/xmldoc/formats/options/skytraq-gps-utc-offset.xml b/xmldoc/formats/options/skytraq-gps-utc-offset.xml index d6656e847..1eef86a85 100644 --- a/xmldoc/formats/options/skytraq-gps-utc-offset.xml +++ b/xmldoc/formats/options/skytraq-gps-utc-offset.xml @@ -1,6 +1,6 @@ gps-utc-offset is used to override the built-in table of offsets of -the offset between GPS time and UTC time. This chipset reports only +the offset between GPS time and UTC time. This chipset reports only GPS time to the host and relies on software to know every time an adjustment is made. Since GPS time offsets can change without a new version of GPSBabel is released, those that care about total accuracy can override it. diff --git a/xmldoc/formats/options/skytraq-gps-week-rollover.xml b/xmldoc/formats/options/skytraq-gps-week-rollover.xml index 9cb344d57..131445a6b 100644 --- a/xmldoc/formats/options/skytraq-gps-week-rollover.xml +++ b/xmldoc/formats/options/skytraq-gps-week-rollover.xml @@ -10,7 +10,7 @@ which roll over to 0 every 1024 weeks (close to 20 years). Starting from: - gps-week-rollover value: + gps-week-rollover value: diff --git a/xmldoc/formats/options/skytraq-last-sector.xml b/xmldoc/formats/options/skytraq-last-sector.xml index 836f46e23..ffe30b687 100644 --- a/xmldoc/formats/options/skytraq-last-sector.xml +++ b/xmldoc/formats/options/skytraq-last-sector.xml @@ -2,4 +2,4 @@ encountered. We observed that sometimes the device doesn't report the correct number of used sectors, which confuses the Windows software, so that it might not get all trackpoints. -In contrast, our algorithm ensures that everything is being read (please report if it doesn't work for you). +In contrast, our algorithm ensures that everything is being read (please report if it doesn't work for you). diff --git a/xmldoc/formats/options/skytraq-targetlocation.xml b/xmldoc/formats/options/skytraq-targetlocation.xml index a132e2ce8..e987dcdeb 100644 --- a/xmldoc/formats/options/skytraq-targetlocation.xml +++ b/xmldoc/formats/options/skytraq-targetlocation.xml @@ -12,9 +12,9 @@ 0 -o unicsv -F - - Sets latitude and longitude of the location finder to N12.34 and - W56.78 respectively. - The arrows on the device will point you to this location as soon as + Sets latitude and longitude of the location finder to N12.34 and + W56.78 respectively. + The arrows on the device will point you to this location as soon as it has a satellite fix. diff --git a/xmldoc/formats/options/subrip-gps_date.xml b/xmldoc/formats/options/subrip-gps_date.xml index 29c15c56d..fa46e31d7 100644 --- a/xmldoc/formats/options/subrip-gps_date.xml +++ b/xmldoc/formats/options/subrip-gps_date.xml @@ -1,13 +1,13 @@ - The date part of the GPS timestamp which corresponds to a known position + The date part of the GPS timestamp which corresponds to a known position in the video. - Format is yyyymmdd. This option must be used together with - ; if one or both are missing, the timestamp of the + Format is yyyymmdd. This option must be used together with + ; if one or both are missing, the timestamp of the first GPS trackpoint is used. - The video position to which the timestamp corresponds can be set with the + The video position to which the timestamp corresponds can be set with the option. diff --git a/xmldoc/formats/options/subrip-gps_time.xml b/xmldoc/formats/options/subrip-gps_time.xml index 844171bdf..da1823619 100644 --- a/xmldoc/formats/options/subrip-gps_time.xml +++ b/xmldoc/formats/options/subrip-gps_time.xml @@ -1,13 +1,13 @@ - The time part of the GPS timestamp which corresponds to a known position + The time part of the GPS timestamp which corresponds to a known position in the video. - Format is hhmmss. This option must be used together with + Format is hhmmss. This option must be used together with ; if one or both are missing, the timestamp of the first GPS trackpoint is used. - The video position to which the timestamp corresponds can be set with the + The video position to which the timestamp corresponds can be set with the option. diff --git a/xmldoc/formats/options/subrip-video_time.xml b/xmldoc/formats/options/subrip-video_time.xml index 69553b571..056205e62 100644 --- a/xmldoc/formats/options/subrip-video_time.xml +++ b/xmldoc/formats/options/subrip-video_time.xml @@ -6,6 +6,6 @@ Format is hhmmss. If omitted, 0:00:00 (beginning of video) is assumed. - The GPS timestamp can be set with the and + The GPS timestamp can be set with the and options. diff --git a/xmldoc/formats/options/text-encrypt.xml b/xmldoc/formats/options/text-encrypt.xml index 2d7d96091..e81c9e4bd 100644 --- a/xmldoc/formats/options/text-encrypt.xml +++ b/xmldoc/formats/options/text-encrypt.xml @@ -1,3 +1,3 @@ -Use this option to encrypt hints from Groundspeak GPX files. +Use this option to encrypt hints from Groundspeak GPX files. diff --git a/xmldoc/formats/options/text-logs.xml b/xmldoc/formats/options/text-logs.xml index 9e25a13ea..ed91b37a0 100644 --- a/xmldoc/formats/options/text-logs.xml +++ b/xmldoc/formats/options/text-logs.xml @@ -1,3 +1,3 @@ -Use this option to include Groundspeak cache logs in the created document. +Use this option to include Groundspeak cache logs in the created document. diff --git a/xmldoc/formats/options/text-nosep.xml b/xmldoc/formats/options/text-nosep.xml index 75e79abf7..c02bbcbb8 100644 --- a/xmldoc/formats/options/text-nosep.xml +++ b/xmldoc/formats/options/text-nosep.xml @@ -1,3 +1,3 @@ -To suppress the dashed lines between waypoints, use this option. +To suppress the dashed lines between waypoints, use this option. diff --git a/xmldoc/formats/options/text-splitoutput.xml b/xmldoc/formats/options/text-splitoutput.xml index 5bf9d4c41..6ca7fcd49 100644 --- a/xmldoc/formats/options/text-splitoutput.xml +++ b/xmldoc/formats/options/text-splitoutput.xml @@ -5,7 +5,7 @@ Example for splitoutput option to text format - If "MyPQ.gpx" contains five waypoints, + If "MyPQ.gpx" contains five waypoints, gpsbabel -i gpx -f MyPocketQuery -o text,split -F blah diff --git a/xmldoc/formats/options/tpg-datum.xml b/xmldoc/formats/options/tpg-datum.xml index f215467ff..7a63f31ba 100644 --- a/xmldoc/formats/options/tpg-datum.xml +++ b/xmldoc/formats/options/tpg-datum.xml @@ -1,6 +1,6 @@ The option 'datum="datum name"' can be used to override the default of NAD27 ("N. America 1927 mean") which is correct for the continental U.S. Any legal datum supported -by GPSBabel may be used. For example, points in Hawaii should +by GPSBabel may be used. For example, points in Hawaii should use "Old Hawaiian_mean". - + diff --git a/xmldoc/formats/options/transform-rptdigits.xml b/xmldoc/formats/options/transform-rptdigits.xml index 690361f86..fce6b0b31 100644 --- a/xmldoc/formats/options/transform-rptdigits.xml +++ b/xmldoc/formats/options/transform-rptdigits.xml @@ -1,13 +1,13 @@ - -This option lets you configure how many digits GPSBabel uses for numbering generated route point names. - - -When GPSBabel creates route points during the transformation process these points are sequentially numbered and named "RPTnnn" where nnn represent the number. By default GPSBabel uses 3 digits for these numbers. Rationale: This way a large number of route points can be uniquely named while the generated names are limited to 6 characters. This limitation is imposed by specific GPS devices. - - -Using this option GPSBabel can be configured to use less or more digits for the generated names. This option is best used in conjunction with the rptname option. - - -Convert a GPX track to a GPX route, deleting the original track, using 2 digits for the generated numbers. -gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptdigits=2 -o gpx -F route.gpx - + +This option lets you configure how many digits GPSBabel uses for numbering generated route point names. + + +When GPSBabel creates route points during the transformation process these points are sequentially numbered and named "RPTnnn" where nnn represent the number. By default GPSBabel uses 3 digits for these numbers. Rationale: This way a large number of route points can be uniquely named while the generated names are limited to 6 characters. This limitation is imposed by specific GPS devices. + + +Using this option GPSBabel can be configured to use less or more digits for the generated names. This option is best used in conjunction with the rptname option. + + +Convert a GPX track to a GPX route, deleting the original track, using 2 digits for the generated numbers. +gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptdigits=2 -o gpx -F route.gpx + diff --git a/xmldoc/formats/options/transform-rptname.xml b/xmldoc/formats/options/transform-rptname.xml index a471bb9ff..33a65cdf4 100644 --- a/xmldoc/formats/options/transform-rptname.xml +++ b/xmldoc/formats/options/transform-rptname.xml @@ -1,12 +1,12 @@ - -With this option you can decide to let GPSBabel name generated route points according to their source track name. - - -GPSBabel creates route points during the transformation process named "RPTnnn" where nnn is a numeric part. - -Using this option GPSBabel can be configured to replace the "RPT" part of the generated names by the name of the source track during the transformation process. This is especially useful if several differently named tracks are contained in the source file which should each be transformed into routes. - - -Convert a GPX track to a GPX route, deleting the original track, naming the generated points like the original track name. -gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptname=y -o gpx -F route.gpx - + +With this option you can decide to let GPSBabel name generated route points according to their source track name. + + +GPSBabel creates route points during the transformation process named "RPTnnn" where nnn is a numeric part. + +Using this option GPSBabel can be configured to replace the "RPT" part of the generated names by the name of the source track during the transformation process. This is especially useful if several differently named tracks are contained in the source file which should each be transformed into routes. + + +Convert a GPX track to a GPX route, deleting the original track, naming the generated points like the original track name. +gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptname=y -o gpx -F route.gpx + diff --git a/xmldoc/formats/options/unicsv-datum.xml b/xmldoc/formats/options/unicsv-datum.xml index b4d56af7f..80b85eae7 100644 --- a/xmldoc/formats/options/unicsv-datum.xml +++ b/xmldoc/formats/options/unicsv-datum.xml @@ -1,4 +1,4 @@ - This option specifies the datum to be used on output. Valid values for this + This option specifies the datum to be used on output. Valid values for this option are listed in . diff --git a/xmldoc/formats/options/unicsv-fields.xml b/xmldoc/formats/options/unicsv-fields.xml index f54897ee2..f21492848 100644 --- a/xmldoc/formats/options/unicsv-fields.xml +++ b/xmldoc/formats/options/unicsv-fields.xml @@ -4,7 +4,7 @@ the command line instead of relying on the first line of your input file describing the file. Field names are separated by a '+' character. The list of field names is exactly that allowed in the first line of a unicsv file without this option. - + Example for unicsv fields option to describe input file. @@ -13,7 +13,7 @@ unicsv file without this option. gpsbabel -i unicsv,fields=lat+lon+description -f file.csv -o gpx -F file.gpx - declares that file.csv has three fields, latitude, longitude, + declares that file.csv has three fields, latitude, longitude, and description, in that order. diff --git a/xmldoc/formats/options/unicsv-utc.xml b/xmldoc/formats/options/unicsv-utc.xml index 4c2964e0e..2c4d062ce 100644 --- a/xmldoc/formats/options/unicsv-utc.xml +++ b/xmldoc/formats/options/unicsv-utc.xml @@ -1,5 +1,5 @@ This option specifies the local time zone to use when writing times. It -is specified as an offset from Universal Coordinated Time (UTC) in hours. +is specified as an offset from Universal Coordinated Time (UTC) in hours. Valid values are from -23 to +23. - + diff --git a/xmldoc/formats/options/xcsv-datum.xml b/xmldoc/formats/options/xcsv-datum.xml index 26519942f..ea17ec5fa 100644 --- a/xmldoc/formats/options/xcsv-datum.xml +++ b/xmldoc/formats/options/xcsv-datum.xml @@ -1,4 +1,4 @@ -This option specifies the GPS datum to be used on read or write. Valid values for this +This option specifies the GPS datum to be used on read or write. Valid values for this option are listed in . diff --git a/xmldoc/formats/options/xcsv-style.xml b/xmldoc/formats/options/xcsv-style.xml index 43baf0378..815467fbb 100644 --- a/xmldoc/formats/options/xcsv-style.xml +++ b/xmldoc/formats/options/xcsv-style.xml @@ -4,7 +4,7 @@ input or written on output. This is not a valid option for the various built-in xcsv-based styles; they have prebuilt style definitions. -For information on the format of xcsv style files, see +For information on the format of xcsv style files, see . diff --git a/xmldoc/formats/options/xcsv-urlbase.xml b/xmldoc/formats/options/xcsv-urlbase.xml index 781e75c4c..44847e279 100644 --- a/xmldoc/formats/options/xcsv-urlbase.xml +++ b/xmldoc/formats/options/xcsv-urlbase.xml @@ -1,5 +1,5 @@ -This option specifies the base name to prepend to a URL on output. This +This option specifies the base name to prepend to a URL on output. This might be useful if an input file contains URLs in a relative format and you need them to be in an absolute format. diff --git a/xmldoc/formats/ricoh.xml b/xmldoc/formats/ricoh.xml index 9c7058a54..8ec050b3e 100644 --- a/xmldoc/formats/ricoh.xml +++ b/xmldoc/formats/ricoh.xml @@ -1,17 +1,17 @@ This is the format for the Ricoh 500SE GPS logging camera. - This camera creates log files on the SD card in a folder name "GPSLOG" that - are named "YYMMDDNN.LOG" where NN increments from 00 through 99. The camera - appends new tracks into the current file, hence the "new track" field. When - the current file reaches about 500K, NN increments and logging continues into - the next file. Therefore, there may be multiple tracks in each log - file, and tracks may span one or more files. + This camera creates log files on the SD card in a folder name "GPSLOG" that + are named "YYMMDDNN.LOG" where NN increments from 00 through 99. The camera + appends new tracks into the current file, hence the "new track" field. When + the current file reaches about 500K, NN increments and logging continues into + the next file. Therefore, there may be multiple tracks in each log + file, and tracks may span one or more files. GPSBabel will recognize the "new track" field and will generate a new track, so if you specify multiple files in the correct order, your tracks will be - automatically split sensibly. + automatically split sensibly. For additional tips, see the diff --git a/xmldoc/formats/s_and_t.xml b/xmldoc/formats/s_and_t.xml index 66400993c..4863faa6e 100644 --- a/xmldoc/formats/s_and_t.xml +++ b/xmldoc/formats/s_and_t.xml @@ -5,14 +5,14 @@ gpsbabel.org - We have an additional page describing how to solve the - traveling salesman problem with - Streets & Trips to efficiently optimize a trip with many stops, such as + We have an additional page describing how to solve the + traveling salesman problem with + Streets & Trips to efficiently optimize a trip with many stops, such as is often made by geocachers. @@ -20,4 +20,4 @@ Since modern versions of Streets and Trips support reading GPX, this format is probably not so useful. - + diff --git a/xmldoc/formats/saplus.xml b/xmldoc/formats/saplus.xml index 611d71dd6..3f4a18741 100644 --- a/xmldoc/formats/saplus.xml +++ b/xmldoc/formats/saplus.xml @@ -1,6 +1,6 @@ - - + + This format is for DeLorme Street Atlas USA 2004 Plus and later. For geocachers importing data from a tool like GSAK or @@ -14,4 +14,4 @@ The second time you import the file do not check any circle and in the second to last column, change URL to none and then click next. Use the same name you used the first time but add -Flag to it. - + diff --git a/xmldoc/formats/saroute.xml b/xmldoc/formats/saroute.xml index fea5e1249..a285a46cc 100644 --- a/xmldoc/formats/saroute.xml +++ b/xmldoc/formats/saroute.xml @@ -1,4 +1,4 @@ - + This format reads route files from many DeLorme mapping products. It supports the anr, rte, and rtd formats as either tracks or routes. @@ -6,4 +6,4 @@ routes. versions of DeLorme software; older versions didn't store the turn information with the route. - + diff --git a/xmldoc/formats/skytraq.xml b/xmldoc/formats/skytraq.xml index 8ff91a393..6c9d90260 100644 --- a/xmldoc/formats/skytraq.xml +++ b/xmldoc/formats/skytraq.xml @@ -11,9 +11,9 @@ use this format to read its memory. - Manufacturer - Model - USB (baud) + Manufacturer + Model + USB (baud) Bluetooth (baud) diff --git a/xmldoc/formats/sportsim.xml b/xmldoc/formats/sportsim.xml index 2be80258a..e6f533bd3 100644 --- a/xmldoc/formats/sportsim.xml +++ b/xmldoc/formats/sportsim.xml @@ -1,14 +1,14 @@ - With this format we support Sportsim trackfiles located in zipped .ssz archives. + With this format we support Sportsim trackfiles located in zipped .ssz archives. - Currently we cannot read zipped files directly with GPSBabel. So you have + Currently we cannot read zipped files directly with GPSBabel. So you have to extract the archive before you can use any file. The trackfiles have .txt extensions. From the Sportsim homepage: - Sportsim provide software applications and web-based graphically + Sportsim provide software applications and web-based graphically simulated performance information and image solutions to outdoor active people. diff --git a/xmldoc/formats/subrip.xml b/xmldoc/formats/subrip.xml index ed981a5c8..3a2259801 100644 --- a/xmldoc/formats/subrip.xml +++ b/xmldoc/formats/subrip.xml @@ -8,7 +8,7 @@ will need to synchronize both. For this purpose, film the display of your GPS receiver (or any other device) showing GPS time. (Important: you need precise GPS time for this; local time, especially from an - inaccurate clock, will not do for this.) + inaccurate clock, will not do for this.) Determine the position in the video at which the GPS time is visible diff --git a/xmldoc/formats/tabsep.xml b/xmldoc/formats/tabsep.xml index 04f7d1fcf..886d318e9 100644 --- a/xmldoc/formats/tabsep.xml +++ b/xmldoc/formats/tabsep.xml @@ -1,7 +1,7 @@ This format, like the custom format, is mainly used for the purpose of testing GPSBabel. It is supposed to contain -one field for each piece of information supported by the +one field for each piece of information supported by the xcsv format writer, but it may not be entirely in sync with the documentation at . diff --git a/xmldoc/formats/tef.xml b/xmldoc/formats/tef.xml index 592632d69..0d4b7917f 100644 --- a/xmldoc/formats/tef.xml +++ b/xmldoc/formats/tef.xml @@ -1,5 +1,5 @@ -TEF, internally called "TourExchangeFormat", is an XML based export format +TEF, internally called "TourExchangeFormat", is an XML based export format used by Map&Guide Motorrad-Routenplaner 2005/06. @@ -7,9 +7,9 @@ Because this is only an export format, GPSBabel does not support writing to this format. -GPSBabel also supports the bcr format, which +GPSBabel also supports the bcr format, which may also be used with this program and supports both reading and writing. gpsbabel -r -i tef,routevia -f in.xml -o gpx -F out.gpx - + diff --git a/xmldoc/formats/text.xml b/xmldoc/formats/text.xml index 28431160b..c429b2493 100644 --- a/xmldoc/formats/text.xml +++ b/xmldoc/formats/text.xml @@ -5,4 +5,4 @@ handy for listings of any type of waypoint files. Groundspeak extensions and writes a text file with encrypted hints: gpsbabel -i gpx -f 12345.gpx -o text,encrypt -F 12345.txt - + diff --git a/xmldoc/formats/tomtom.xml b/xmldoc/formats/tomtom.xml index 5da5edc35..988f7dd5b 100644 --- a/xmldoc/formats/tomtom.xml +++ b/xmldoc/formats/tomtom.xml @@ -1,6 +1,6 @@ - - + + This format can read and write TomTom .ov2 (POI) files, as used by the TomTom GO and TomTom Navigator. It has been tested with an original TomTom GO running version 5.00 of the TomTom @@ -12,4 +12,4 @@ gpsbabel-misc mailing list to contact a developer. .bmp file for the icon. It should be 22x22 and 16 colors, and have the same name (not including the extension) as the .ov2 file. - + diff --git a/xmldoc/formats/tpg.xml b/xmldoc/formats/tpg.xml index 68cbada63..71e37f3ad 100644 --- a/xmldoc/formats/tpg.xml +++ b/xmldoc/formats/tpg.xml @@ -1,8 +1,8 @@ - - + + National Geographic Topo! Waypoint and Route Format. This module reads and writes .TPG files created by various editions of NG Topo! Reading/writing of route data is not supported yet.Contributed by Alex Mottram. - + diff --git a/xmldoc/formats/tpo.xml b/xmldoc/formats/tpo.xml index 9b9149dfd..5a39bd3d2 100644 --- a/xmldoc/formats/tpo.xml +++ b/xmldoc/formats/tpo.xml @@ -1,6 +1,6 @@ - - + + This module reads .TPO files created by various editions of NG Topo!. For version 2.x files it will only read tracks. For version 3.x files it will read Tracks/Routes/Waypoints/Map @@ -9,4 +9,4 @@ waypoints.2.x support contributed by Steve Chamberlin. 3.x support contributed by Curt Mills. - + diff --git a/xmldoc/formats/tpo2.xml b/xmldoc/formats/tpo2.xml index fe1cde696..237d8c077 100644 --- a/xmldoc/formats/tpo2.xml +++ b/xmldoc/formats/tpo2.xml @@ -1,9 +1,9 @@ - This module reads tracks from .TPO files created by + This module reads tracks from .TPO files created by National Geographic Topo! version 2.x - Contributed by Steve Chamberlin. + Contributed by Steve Chamberlin. - + diff --git a/xmldoc/formats/vcard.xml b/xmldoc/formats/vcard.xml index f365dadb0..6e76b032d 100644 --- a/xmldoc/formats/vcard.xml +++ b/xmldoc/formats/vcard.xml @@ -1,6 +1,6 @@ - - + + The vCard output is intended to be in a format that enables waypoints to be viewed with an Apple iPod. This is achieved by mapping waypoint fields into vCard fields that can be displayed as @@ -8,6 +8,6 @@ mapping waypoint fields into vCard fields that can be displayed as iPod manual for instructions), the resulting VCF file should be moved into the iPod 'Contacts' folder. As an alternative, Mac OS X users may prefer to drag the VCF file into their address book and synchronize -with the iPod using iSync. +with the iPod using iSync. - + diff --git a/xmldoc/formats/wbt.xml b/xmldoc/formats/wbt.xml index 1fa9f10af..2e5f08a96 100644 --- a/xmldoc/formats/wbt.xml +++ b/xmldoc/formats/wbt.xml @@ -1,7 +1,7 @@ -Serial download protocol for the +Serial download protocol for the Wintec WBT-200 and -Wintec WBT-201 -Wintec WBT-1000 +Wintec WBT-201 +Wintec WBT-1000 GPS data loggers. Although untested it is expected that this will also support the WBT-100. Wintec WBT-201 @@ -14,14 +14,14 @@ GPS data loggers. Although untested it is expected that this will also support t Internally, this is actually a serial device that has a serial/USB adapter built into it. It uses the CP210x chip by Silicon labs. You will probably -need a driver for this chip. The product ships with one for Windows. -The Linux 210x driver seems to work fine. Mac users will need to download +need a driver for this chip. The product ships with one for Windows. +The Linux 210x driver seems to work fine. Mac users will need to download the Mac driver for CP210x. GPSBabel does not try to offer an interface to configure these units. That -is left to the Windows software that comes with it or tools like the +is left to the Windows software that comes with it or tools like the WBT 201 Viewer for Mac OS/X and Linux. diff --git a/xmldoc/formats/wintec_tes.xml b/xmldoc/formats/wintec_tes.xml index 29c16fd75..86c9919fc 100644 --- a/xmldoc/formats/wintec_tes.xml +++ b/xmldoc/formats/wintec_tes.xml @@ -1,11 +1,11 @@ -This format supports Wintec .tec files, such as appear on the +This format supports Wintec .tec files, such as appear on the Wintec WBT-202 data logger. The WinTec WBT-202 stores tracks and waypoints on an internal MICRO-SD Memory card. The log files can be accessed by connecting to an USB host and setting the device into a mass storage device (MSD) mode. To enter -this mode, attach it to the computer, then hold the power button until the +this mode, attach it to the computer, then hold the power button until the GPS and Bluetooth LEDs go out. It will then behave like an USB Memory stick. and individual files containing your tracks will show up on the "disk" with names ending in .tes. You can use GPSBabel to read these files directly @@ -16,11 +16,11 @@ Note that this format is for the TES files on the GPS, it has no relationship to the .TK2 files created by Wintec's Time Machine software for Windows. -Despite the physical similarity to the +Despite the physical similarity to the Wintec WBT-201, this is believed to be a rather -different product. While this GPS probably works fine for -realtime tracking over the bluetooth or +different product. While this GPS probably works fine for +realtime tracking over the bluetooth or serial lines (once you have appropriate serial drivers), it's expected -to not work with GPSBabel's GPSBabel WBT +to not work with GPSBabel's GPSBabel WBT Protocol module. diff --git a/xmldoc/formats/xcsv.xml b/xmldoc/formats/xcsv.xml index cc2e9e2ab..88f55dfef 100644 --- a/xmldoc/formats/xcsv.xml +++ b/xmldoc/formats/xcsv.xml @@ -1,14 +1,14 @@ -This format is a very flexible module that can be used to read or write -nearly any plain-text record-based waypoint file. This flexibility is -achieved by combining this format with "style" files that describe the +This format is a very flexible module that can be used to read or write +nearly any plain-text record-based waypoint file. This flexibility is +achieved by combining this format with "style" files that describe the format of the waypoint files. -There are several formats built in to GPSBabel that use the underlying xcsv +There are several formats built in to GPSBabel that use the underlying xcsv machinery. Each of those formats takes the same options as the xcsv format, -with the obvious exception of the option. -Those formats are all based on style files that can be found in +with the obvious exception of the option. +Those formats are all based on style files that can be found in the "style" directory in the GPSBabel source distribution. -- 2.30.2